On Sat, Jun 18, 2011 at 9:18 AM, Aaron Konstam <akonstam@xxxxxxxxxxxxx> wrote: > On Fri, 2011-06-17 at 19:01 -0400, Sam Varshavchik wrote: >> Petrus de Calguarium writes: >> >>> To start it during this session: >>> systemctl start <service name>.service >>> >>> To start every time you start graphical.target: >>> systemctl enable <service name>.service >>> >>> I'm not sure how you would differentiate between multi-user.target and >>> graphical.target. >> >> This is specified by the service unit. systemd uses a slightly different >> paradigm. The service itself knows what system state it should be running >> in, by default. Enabling the service puts it as a target for the state. > > Now II am really confused. How does a service like sshd.service know > what system state it is to run at For sysvinit services, it probably looks at the "/etc/init.d/" script headers. For example, you have to start the nfs server after installing it. "/etc/init.d/nfs" has --- 8< --- chkconfig - 30 60 --- >8 --- in its "checkconfig" header section and --- 8< --- Required-Start: $local_fs $network $syslog $rpcbind Required-Stop: $local_fs $network $syslog $rpcbind Defaul-Stop: 0 1 6 --- >8 --- in its LSB header section. Running "systemctl enable nfs" set it up to start in runlevels 2 3 4 5 and stop in runlevels 0 1 6 in the same way that "chkconfig nfs on" would (in fact, since the nfs server's a legacy service, there's a message that systemctl's handing over to chkconfig - I've forgotten the actual wording). Since runlevels 2 3 4 are symlinked to multi-user.target, ... For systemd services, it probably looks at the "Unit" section of the "*.service" files in "/lib/systemd/system/". -- 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
