systemd - pid not readable (yet?) after start - multiple services

[divinorum]

you solution does not work to me on F17

---------- Post added at 11:02 AM ---------- Previous post was at 10:51 AM ----------

There is something like this in httpd.conf, what I have missed before. But it's does not help too

# PidFile: The file in which the server should record its process
# identification number when it starts. Note the PIDFILE variable in
# /etc/sysconfig/httpd must be set appropriately if this location is
# changed.

[modal1]

I updated to FC18 and the problem started again with spamass-milter failing on boot. There are still the complaints for httpd, smbd, nmbd in the messages log but those seem to launch successfully on boot.
Restarting the service succeeds.

It's great having systemd for faster boot, but honestly, how often does anyone reboot a linux server beyond kernel upgrades?

[jpollard]

Thats why it was a stupid justification for systemd.

IT works acceptably well for simple things, but when configurations start getting complex it fails due to the lack of control the admin has over it.

[modal1]

Feels like change for the sake of change.

[jpollard]

It always did.

the only improvement is the startup time. The big loss is the control, and secondarily, the merged requirement of udev and dbus.

If either udev or (especially) dbus fails, the system crashes. VERY bad thing for servers.

[stevea]

Right - the only advantage is startup time, and that was the main reason ....
Sad to see senility set in.

[jpollard]

It certainly seems to be the only reason.

Hard to control, hard to configure, hard to get working... and easy to fail.

Anything complicated and it falls down.