Thanks for the info. Now, why it shouldn't have cleaned itself up when I
gave it the reboot command... I see too many (that's defined as more than
zero) cases where systemd WANTS TO BOOT FAST, and doesn't wait for things
to finish - sush as not getting the hostname from dhcp, and so having to
hardcode the name instead.
Systemd, as I've said before, seems to be targeted towards laptops. Not
servers. Not workstations. *bleah*
I'm still thinking it's a jacked up filesystem. I'm not sure what fs
you're using, though the default is xfs, but I'd look at dmesg and
boot.log to see if the kernel is finding issues with the drives or just
the fs. It's also possible that server had been up a long time and RAM
was funky. I've seen both of these happen before.
As far as using systemd based systems on servers, a month or so back, I
pushed a new C7 kickstart for servers we send to customers and haven't
seen anything to make me think systemd isn't good for servers. That
doesn't mean it's not a giant POS for administrators. If only they
hadn't jacked the syntax all to hell from initd, I might be slightly
happier with it. That by itself has to be the most ridiculous thing any
group of devs have ever done. And for no rational reason either. </endrant>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
