On Thu, 26 Nov 2015 19:00:45 -0700 Stephen Rogers
wrote:
> Had this same problem on Debian Stretch. Tried many different things to
> get the startup order proper but I could only seem to move the problem
> from startup to shutdown and back.Â
>
> Finally this combination of
Had this same problem on Debian Stretch. Tried many different things to
get the startup order proper but I could only seem to move the problem
from startup to shutdown and back.
Finally this combination of options in my fstab seemed to get systemd
to both startup and shutdown in the right order.
On 07/09/2015 at 21:33 -0300, Javier Ayres wrote:
> The drive is mounted correctly at startup, but if I don't manually unmount it
> before shutting down the system will take 30 minutes to shut down. The message
> "A stop job is running for /mnt/D3 (0s / 1min 30s)" is shown; after 90 seconds
> it
I tried adding x-systemd.requires=NetworkManager.service in fstab and it
works when starting the system up, but it still makes me wait 30 minutes
when shutting down.
2015-09-10 12:08 GMT-03:00 Javier Ayres :
> What I mean is to start the NFS mounting service after
Trying to manually unmount the drive with the network down blocks (with CPU
at 100%) indefinitely, or so it appears. I waited 40 minutes and then
canceled it because I had to go.
Can't the service which mounts/unmounts NFS (not sure which one that is) be
put after NetworkManager?
2015-09-09
Am 10.09.2015 um 16:50 schrieb Michael Biebl:
> Am 10.09.2015 um 16:19 schrieb Javier Ayres:
>> Can't the service which mounts/unmounts NFS (not sure which one that is) be
>> put after NetworkManager?
>
> I guess you mean *before*. But well, as I tried to explain, currently
> that doesn't work
What I mean is to start the NFS mounting service after NetworkManager,
which would also mean to stop it before NetworkManager, right? I didn't
know network.target is the service that mounts NFS shares, in which case
now I understand that what I'm asking is what you explained that is not
possible.
Am 10.09.2015 um 16:19 schrieb Javier Ayres:
> Trying to manually unmount the drive with the network down blocks (with CPU
> at 100%) indefinitely, or so it appears. I waited 40 minutes and then
> canceled it because I had to go.
This is probably a problem on its own.
> Can't the service which
Am 09.09.2015 um 05:09 schrieb Javier Ayres:
> I edited the wpa_supplicant service as you suggested but the issue is still
> present.
Hm, right. The issue here is, that you are using NetworkManager.service
to bring up your (wireless) interface. Unfortunately we can't bring up
Am 08.09.2015 um 02:33 schrieb Javier Ayres:
> Package: systemd
> Version: 225-1
> Severity: normal
>
> I have a NFS share configured in my /etc/fstab as follows:
>
> 192.168.1.4:/mnt/samsung /mnt/D3 nfs
> auto,nofail,timeo=25,users,_netdev,bg,comment=x-gvfs-show 0 0
>
> The
Hi, I'm connecting via wifi and using NetworkManager. This is
NetworkManager's configuration file for this particular network:
[connection]
id=natalia
uuid=c0a08844-145f-4c9d-8528-2163efcfba50
type=802-11-wireless
timestamp=1396749922
[802-11-wireless]
ssid=natalia
mode=infrastructure
Am 08.09.2015 um 16:54 schrieb Javier Ayres:
> Hi, I'm connecting via wifi and using NetworkManager. This is
> NetworkManager's configuration file for this particular network:
>
> [connection]
> id=natalia
> uuid=c0a08844-145f-4c9d-8528-2163efcfba50
> type=802-11-wireless
> timestamp=1396749922
>
I edited the wpa_supplicant service as you suggested but the issue is still
present. I've also found that the behavior is not consistent, sometimes it
waits 90 seconds and sometimes it waits 30 minutes (even after changing the
fstab entry).
2015-09-08 14:01 GMT-03:00 Michael Biebl
Processing control commands:
> severity -1 important
Bug #798314 [systemd] systemd: Systemd waits 30 minutes to shut down because of
NFS share
Severity set to 'important' from 'normal'
--
798314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798314
Debian Bug Tracking System
Contact
14 matches
Mail list logo