On 19/12/11 10:26, Stefan Seyfried wrote:
Am 17.12.2011 18:54, schrieb Cristian RodrÃguez:
ln -s /lib/systemd/system/postfix.service /etc/systemd/system/multi-user.target.wants
and now it starts.
You have to use systemctl enable postfix.service, the symlink is created as a result of that command.
This is like great but how was I supposed to come up with this?
man systemctl ?
see also my other mail: even old-fashioned "chkconfig postfix" would have told.
However, there are obviously some bugs in the update process from sysv to systemd which lead to services being disabled which were not before.
It's all part of a learning curve of which stumbling is a part of the early steps. With systemd replacing or superceding sysvinit I and I'm sure many othere expected it to be a seamless transition.
What we had here was an incomplete duplication of the services automatically launched by systemd, i.e you see a service missing and then having to dig into lots of documentation to discover the reason.
It would have been kinder to have provided a README or some such with what was supported and what was on the todo list. It needen't have been a long treatise but it would have helped in avoiding surprises. Even an pointer to the URL's given here in the last day or so would have forewarned and informed users better.
If I were a sysadmin, I would consign systemd to a test machine until I was 100% certain it was a safe replacement for sysvinit - mid 2012 timeline perhaps. I suppose current users are performing the testing role and reporting back in an effort to highlight problems and misconceptions so they can be dealt with as surely they will be and systemd difficulties will melt away perhaps even much quicker than the massive and disruptive change to glibc if anyone can remember that far back. Upstart has caused similar though small ripples on Ubuntu. Regards Sid.