On 02/17/2014 11:30 PM, John Paul Adrian Glaubitz wrote: > I think a first thing to test might be the latest version which > is now in unstable together with systemd.
I did some tests now with the result that by default rpcbind.service is
actually properly loaded now which wasn't the case when I first
made my experiments with systemd and rpcbind back when I reported
this bug:
=======================================================================
root@jessie32:~> systemctl status rpcbind.service
rpcbind.service - LSB: RPC portmapper replacement
Loaded: loaded (/etc/init.d/rpcbind)
Active: active (running) since Tue 2014-02-18 00:04:18 CET; 7min ago
Process: 417 ExecStart=/etc/init.d/rpcbind start (code=exited,
status=0/SUCCESS)
CGroup: name=systemd:/system/rpcbind.service
└─469 /sbin/rpcbind -w
Feb 18 00:04:17 jessie32 systemd[1]: Starting LSB: RPC portmapper
replacement...
Feb 18 00:04:18 jessie32 systemd[1]: Started LSB: RPC portmapper
replacement.
root@jessie32:~>
=======================================================================
However, the NFS mount (/home in my case) is not performed by default:
=======================================================================
root@jessie32:~> systemctl status home.mount
home.mount - /home
Loaded: loaded (/etc/fstab)
Active: inactive (dead)
Where: /home
What: home:/srv/home
root@jessie32:~>
=======================================================================
Which isn't really a problem when you add "comment=systemd.automount"
to your NFS mounts in /etc/fstab:
=======================================================================
root@jessie32:~> grep home /etc/fstab
home:/srv/home /home nfs
vers=3,nosuid,nodev,intr,tcp,comment=systemd.automount 0 0
root@jessie32:~>
=======================================================================
This will define NFS mounts as automounts which are in the waiting
state upon startup:
=======================================================================
root@jessie32:~> systemctl status home.automount
home.automount
Loaded: loaded (/etc/fstab)
Active: active (waiting) since Tue 2014-02-18 00:04:16 CET; 8min ago
Where: /home
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
root@jessie32:~>
=======================================================================
The moment you access the directory /home, home.mount is becoming
active:
=======================================================================
root@jessie32:/home> systemctl status home.mount
home.mount - /home
Loaded: loaded (/etc/fstab)
Active: active (mounted) since Tue 2014-02-18 00:20:25 CET; 2s ago
Where: /home
What: home:/srv/home
Process: 1864 ExecMount=/bin/mount home:/srv/home /home -t nfs -o
vers=3,nosuid,nodev,intr,tcp,comment=systemd.automount (code=exited,
status=0/SUCCESS)
Feb 18 00:20:25 jessie32 systemd[1]: Mounting /home...
Feb 18 00:20:25 jessie32 systemd[1]: Mounted /home.
root@jessie32:/home>
=======================================================================
So, it might not be important to have socket activation in rpcbind. At
least in Debian, rpcbind is still started through LSB init scripts on
systemd instead of a unit file or socket activation and probably
because of the service "quotarpc.service" which is already wanted
by the target "basic.target".
As for the NFS mounts, it seems weird to me that those aren't mounted
when the target "remote-fs.target" is reached:
=======================================================================
root@jessie32:~> systemctl list-units --type=target
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network-online.target loaded active active Network is Online
paths.target loaded active active Paths
printer.target loaded active active Printer
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded active active Syslog
timers.target loaded active active Timers
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
16 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@jessie32:~>
=======================================================================
I have to investigate more as to what the reason for this is. Might
be related to the fact that I defined the /home mount as an automount
in systemd.
Cheers,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
signature.asc
Description: OpenPGP digital signature
