You are not logged in.

#1 2012-11-02 03:01:08

nuc
Member
Registered: 2012-04-26
Posts: 119

[SOLVED] Enabling ntpd systemd service

Hi,
There are some inconsistencies in the wiki. Here it says that the ntpd service is enabled by "systemctl enable ntpd" and here it says by "systemctl enable ntpd.service".
So whats right? Both?

Last edited by nuc (2013-02-07 18:13:39)

Offline

#2 2012-11-02 03:02:20

h54
Member
Registered: 2011-11-22
Posts: 96

Re: [SOLVED] Enabling ntpd systemd service

systemctl enable ntpd.service is the only one that worked for me.  This is fresh install, if that matters.

Offline

#3 2012-11-02 03:04:42

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Enabling ntpd systemd service

Service files all have the .service suffix: you should be able to use bash completion to print out the full name.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#4 2012-11-02 03:04:54

nuc
Member
Registered: 2012-04-26
Posts: 119

Re: [SOLVED] Enabling ntpd systemd service

Thank you very much.
Could someone comment on why both commands are on the wiki?

Offline

#5 2012-11-02 03:10:01

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [SOLVED] Enabling ntpd systemd service

Because they should both work; ".service" is assumed.

Offline

#6 2012-11-02 03:10:31

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,648

Re: [SOLVED] Enabling ntpd systemd service

Read the systemd wiki page.

When using systemctl, you generally have to specify the complete name of the unit file, including its suffix, for example sshd.socket. There are however a few shortforms when specifying the unit in the following systemctl commands:

If you don't specify the suffix, systemctl will assume .service. For example, netcfg and netcfg.service are treated equivalent.

Last edited by 2ManyDogs (2012-11-02 03:14:17)

Offline

#7 2012-11-02 03:22:48

endived
Member
Registered: 2011-06-14
Posts: 9

Re: [SOLVED] Enabling ntpd systemd service

nuc wrote:

Thank you very much.
Could someone comment on why both commands are on the wiki?

Both should work since the latest systemd update.  Allan McRae hinted at this in his blogpost (or somewhere down in the comments):    http://allanmcrae.com/2012/08/are-we-re … rch-linux/

Can't seem to find any news about this but I've noticed that # systemctl stop foo effectively stops the foo daemon, as well as # systemctl stop foo.service.
I've tried with sshd and gdm.

Last edited by endived (2012-11-02 03:23:56)

Offline

Board footer

Powered by FluxBB