On Sunday, June 05, 2011 12:20:13 Joe Zeff wrote:
> On 06/05/2011 06:49 AM, Garry T. Williams wrote:
> > This may be a systemd bug. Enabling sendmail.service is
> > ineffective after a reboot. I still have to manually start this
> > service after boot.
>
> Up through F14 there was a Gnome control panel (under
> Administration) called Services. It allowed you to control which
> services started at boot and in which runlevels. If it's still
> there in F15 and Gnome3, it's probably what you want to use.
OK, I should have mentioned that chkconfig --list sendmail clearly
shows that it is enabled.
The "Services" application is no longer very useful[*]. The systemd
way is:
systemctl enable sendmail.service
This succeeds; chkconfig verifies that, but the systemd unit still is
not started at boot time.
The simple work-around for now is to run
systemctl start sendmail.service
after boot or to add the command to rc.local .
Finally, the problem has been reported:
https://bugzilla.redhat.com/show_bug.cgi?id=704393
_____________________
[*] Although I don't run Gnome, the application is
system-config-services and it is offered by KDE under the
Administration menu. It seems, judging from the UI, that it will
allow starting, stopping and restarting only. The enable and disable
icons are disabled. Curiously, chkconfig will enable and disable
legacy SysV services.
All this will eventually be sorted out because the SysV init scripts
will be replaced by systemd units. See
https://fedoraproject.org/wiki/Features/SysVtoSystemd .
--
Garry Williams
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
