Sep 12 18:28:30 XPS15 NetworkManager: dhcp4 (eth0): state changed bound -> terminated Sep 12 18:28:30 XPS15 NetworkManager: dhcp4 (eth0): canceled DHCP transaction Sep 12 18:28:30 XPS15 NetworkManager: device (eth0): state change: deactivating -> disconnected (reason 'connection-removed', sys-iface-state: 'managed') Sep 12 18:28:30 XPS15 init: Trying to re-exec init Sep 12 18:28:30 XPS15 root: Unmounted NFS shares successfully. Sep 12 18:28:30 XPS15 root: Unmounting NFS shares gracefully before the network goes down. Sep 12 18:28:30 XPS15 dbus-daemon: Successfully activated service '_dispatcher' Sep 12 18:28:30 XPS15 dbus-daemon: Activating service name='_dispatcher' requested by ':1.1' (uid=0 pid=1761 comm="/usr/sbin/NetworkManager -pid-file /run/NetworkMa" label="kernel") (using servicehelper) Sep 12 18:28:30 XPS15 NetworkManager: manager: NetworkManager state is now DISCONNECTING Sep 12 18:28:30 XPS15 NetworkManager: device (eth0): state change: activated -> deactivating (reason 'connection-removed', sys-iface-state: 'managed') Sep 12 18:28:30 XPS15 init: Switching to runlevel: 6 Sep 12 18:28:30 XPS15 shutdown: shutting down for system reboot Or in more general wording: how can I change the shutdown sequence of services? Question: how can I change the init.d/conf/OpenRC in such a way that Syncthing stops before NetworkManager? If I manually shutdown Syncthing before I shutdown the system the 'flock' error is not present. I would expect that when I shutdown the system, syncthing would stop before NetworkManager. This is a good thing since Syncthing relies on network/internet connectivity. Syncthing will wait untill NetworkManager is running. Synchting has a 'depend' section in its init.d file: More specifically these two services play a role: But after some digging and trial&error on my system I track the issue down to one of the services. There is not much that I could find online regarding this error. During each shutdown/restart I get this error (often 2 times):Ĭall to flock failed: Resource temporarily unavailable There is however one annoyance that I cannot seem to fix. I really love OpenRC, especially it's simplicity over systemd. Posted: Sun 4:43 pm Post subject: OpenRC shutdown sequence Gentoo Forums Forum Index Other Things Gentoo Now try to check each of them and ensure none of them are reading from the mounted drive with the issue, this should resolve your problem after you have found the specific one.Gentoo Forums :: View topic - OpenRC shutdown sequence dropbox, antivirus, some gaming software, a gamebox every single application that is not ran by the system and auto starts with your machine. Now how does this help you.firstly check which applications start with your machine ie. For example in my case at the time it was a software called "Everything" which is basically a harddrive index searching software and in it I had the saved mounted drive as one of the drives I was reading from. ![]() ![]() The reason it keeps reappearing is due to a application you have installed that reads from that mounted drive. Okay for everyone having this issue whether it is Windows 7 or 10 or any other version of windows and have tried the net use commands along with registry deletes and the drive reappears I can tell you what the issue is, however its up to you to find it specifically. The drive does not show up for users other than myself. Rebooting back to normal mode the drive is back as usual. Update: When booting in safe mode with networking the bad drive doesn't appear at all, though my other network drives do. What else could cause this drive to keep showing up and how can I get rid of it? But the drive still merrily shows up every reboot. Reg delete HKCU\Network\Z /f Turns out this key doesn't exist, there is no P in my HKEY_CURRENTUSER\NETWORK\ key. ![]() ![]() Net use z: \\server\path /persistent:no was another suggestion, I tried deleting the drive with the above command, then remapped it using this command, didn't work. Net use /d z: deletes the drive but it comes back at login. On restart the original drive reappeared. "Disconnect" from the right click menu in Computer (this worked for other mapped drives, not for this one)ĭisconnecting the drive and remapping a drive to that letter with the "reconnect at login" option disabled. I've tried all solutions posted at this similar question but none have worked after reboot. It was set to "reconnect at login" and it seems impossible to remove. I mistakenly mapped my P: drive in Windows 7 to a useless network share, and for the life of me I can't remove the network drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |