Le samedi 03 septembre 2011 à 13:43 +0300, Vahis a écrit :
On 03.09.2011 12:05, Vahis wrote:
The NFS client lost all shares.
# mount -a Starting rpc.statd ... portmapper not running failed mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
I was able to get NFS client running by YaST > System > Runlevel
I started statd there. It didn't want to first but then it added something and started running. Now NFS client works (the mounts are in fstab as the 'mount -a' reveals.
Please open a bug report for this.
And tens of other stuff.
Systemctl shows 117 active units.
Systemctl --failed lists these:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION NetworkManager.service loaded failed failed Network Manager dev-sda1.swap loaded failed failed /dev/sda1
These are apparently ones that been tried to run but they fail. I don't see why NetworkManager should be started at all though.
Because we don't know if NM should be started or not : the configuration is part of another file (/etc/sysconfig/network/config, NETWORKMANAGER file). So, NM service is always "enabled" but there is a precondition which checks for /etc/sysconfig/network/config and cause the service to fail if set to NO).
OTOH swap seems to work according to top.
swapon -s is better to check that. Give also systemctl status dev-sda1.swap output.
There are tens more, some I know by name like
apparmor.service error inactive dead apparmor.service
I've never known that I would have needed it anyway.
inactive = not enabled dead = not running Check the status to get more info. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org