On 20/11/14 13:44, Patrick Matthäi wrote:
> Am 20.11.2014 um 14:03 schrieb Simon McVittie:
>> the output of:
>>
>> systemctl status nfs-common.service
>> systemctl show nfs-common.service
>>
>> and the same for rpcbind.service, rpcbind.target, paths.target and
>> basic.target (i.e. the stuff implicated in your dependency loop).
>> If the "systemctl status" calls list any "Drop-In" files, please also
>> provide those.
>
> Should I provide them after a reboot (without manual starting the nfs
> services) or just while they are running?
Either way is fine; no need to reboot, but if you have done manual steps
to recover the situation since the problematic boot, it would be great
if you could also say what those were.
I'm really more interested in the configuration than the current state;
the status and show subcommands are just a convenient way to collect
everything systemd knows about the service, and be sure you haven't
missed anything.
> There is *one* service (init
> service) on this machine which comes not from the Debian repositorie:
> vmware-tools (from vSphere 5.1 in version 9.0.13.38765 (build-2126665)).
When you say "init service" do you mean a LSB init script in /etc/init.d
with no corresponding systemd unit?
Just to be sure, please tell me what its dependencies are like (if it's
an LSB script, that means Required-Start etc.) and whether it tries to
run in rcS/sysinit.target. If it doesn't try to run until
rc2/multi-user.target it's probably irrelevant though.
S
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
