[arch-general] Final step before changing to systemd
Hi all :) I have almost everything in place to jump to systemd and I hope to make the transition after reading your responses here. Basically I need to know how to handle these daemons: hwclock dbus netfs As today I still have them in the rc.conf DAEMONS field but I was unable to find a way to enable them within systemd. Any suggestions? Regards.
[2012-10-15 22:25:58 -0300] Martín Cigorraga:
Basically I need to know how to handle these daemons: hwclock
Ditch it. Use NTP instead: sudo pacman -Syu ntp systemctl start ntpd.service
dbus
Do nothing. It will be automatically pulled by services that need it.
netfs
Well, do you actually have network filesystems you wish to mount? -- Gaetan
On Mon, Oct 15, 2012 at 10:50 PM, Gaetan Bisson <bisson@archlinux.org>wrote:
[2012-10-15 22:25:58 -0300] Martín Cigorraga:
Basically I need to know how to handle these daemons: hwclock
Ditch it. Use NTP instead:
sudo pacman -Syu ntp systemctl start ntpd.service
dbus
Do nothing. It will be automatically pulled by services that need it.
Excellent.
netfs
Well, do you actually have network filesystems you wish to mount?
-- Gaetan
Yes I do, I have several NFS4 shares in my household network but I'm looking forward to implement Avahi/Zeroconf instead since NFS4 takes ages to give up at boot if the servers are offline. Should I still enable the service then? Thank you!
[2012-10-15 22:56:26 -0300] Martín Cigorraga:
On Mon, Oct 15, 2012 at 10:50 PM, Gaetan Bisson <bisson@archlinux.org>wrote:
Well, do you actually have network filesystems you wish to mount?
Yes I do, I have several NFS4 shares in my household network but I'm looking forward to implement Avahi/Zeroconf instead since NFS4 takes ages to give up at boot if the servers are offline. Should I still enable the service then?
I have no idea but I found this nifty page for you: https://wiki.archlinux.org/index.php/Systemd#Remote_filesystem_mounts "Systemd automatically makes sure that remote filesystem mounts like NFS or Samba are only started after the network has been set up. Therefore remote filesystem mounts specified in /etc/fstab should work out of the box." Sounds like a winner. Enjoy! -- Gaetan
I have no idea but I found this nifty page for you:
https://wiki.archlinux.org/index.php/Systemd#Remote_filesystem_mounts
"Systemd automatically makes sure that remote filesystem mounts like NFS or Samba are only started after the network has been set up. Therefore remote filesystem mounts specified in /etc/fstab should work out of the box."
Sounds like a winner. Enjoy!
-- Gaetan
Awesome. I just did the change, so far so good, the transition is quite smooth, however I still have some minor issues I still need to resolve. Thank you very much!
Am 16.10.2012 03:56, schrieb Martín Cigorraga:
On Mon, Oct 15, 2012 at 10:50 PM, Gaetan Bisson <bisson@archlinux.org>wrote:
[2012-10-15 22:25:58 -0300] Martín Cigorraga:
Basically I need to know how to handle these daemons: hwclock
Ditch it. Use NTP instead:
I think systemd does hwclock handling in some way. However, you should always run NTP, on every machine, real or virtual.
netfs
Well, do you actually have network filesystems you wish to mount?
-- Gaetan
Yes I do, I have several NFS4 shares in my household network but I'm looking forward to implement Avahi/Zeroconf instead since NFS4 takes ages to give up at boot if the servers are offline. Should I still enable the service then? Thank you!
Some tips: 1) Use the _netdev option in fstab. This makes sure systemd knows they are network file systems and acts accordingly. Also make sure you have the very latest nfs-utils, as the rpc-idmapd and rpc-gssd units have been fixed there. 2) If you don't want to wait during boot, use the x-systemd.automount,noauto option. This will mount the file systems on demand.
On Tue, Oct 16, 2012 at 6:10 AM, Thomas Bächler <thomas@archlinux.org>wrote:
Am 16.10.2012 03:56, schrieb Martín Cigorraga:
On Mon, Oct 15, 2012 at 10:50 PM, Gaetan Bisson <bisson@archlinux.org wrote:
[2012-10-15 22:25:58 -0300] Martín Cigorraga:
Basically I need to know how to handle these daemons: hwclock
Ditch it. Use NTP instead:
I think systemd does hwclock handling in some way. However, you should always run NTP, on every machine, real or virtual.
netfs
Well, do you actually have network filesystems you wish to mount?
-- Gaetan
Yes I do, I have several NFS4 shares in my household network but I'm looking forward to implement Avahi/Zeroconf instead since NFS4 takes ages to give up at boot if the servers are offline. Should I still enable the service then? Thank you!
Some tips: 1) Use the _netdev option in fstab. This makes sure systemd knows they are network file systems and acts accordingly. Also make sure you have the very latest nfs-utils, as the rpc-idmapd and rpc-gssd units have been fixed there.
2) If you don't want to wait during boot, use the x-systemd.automount,noauto option. This will mount the file systems on demand.
Wow, that's great to know, thank you =)
On Tue, Oct 16, 2012 at 11:10:21AM +0200, Thomas Bächler wrote:
Am 16.10.2012 03:56, schrieb Martín Cigorraga:
On Mon, Oct 15, 2012 at 10:50 PM, Gaetan Bisson <bisson@archlinux.org>wrote:
[2012-10-15 22:25:58 -0300] Martín Cigorraga:
Basically I need to know how to handle these daemons: hwclock
Ditch it. Use NTP instead:
I think systemd does hwclock handling in some way. However, you should always run NTP, on every machine, real or virtual.
systemd reimplements the bare minimum of hwclock(8) to "seal" the kernel timezone, as the first call to settimeofday(2) on bootup is special. The userspace timezone used will warp the kernel's clock by a given number of minutes -- this means 0 for UTC, and some non-zero value for localtime (UTC offset in hours * 60). This is an ugly hack, and part of why it's never recommended to run with the BIOS clock in localtime. Any regular adjustment of the hwclock should be handled by an NTP daemon, which can read from an authoritative source. d
participants (4)
-
Dave Reisner
-
Gaetan Bisson
-
Martín Cigorraga
-
Thomas Bächler