Results 1 to 10 of 10
Hi there everyone,
I'm having an issue with Ubuntu. To be honest, this problem has always existed, it's nothing new. Nobody seems willing to squash the bug though.
With networked ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-18-2009 #1
networked drives and shutdown/startup order--need help altering
Hi there everyone,
I'm having an issue with Ubuntu. To be honest, this problem has always existed, it's nothing new. Nobody seems willing to squash the bug though.
With networked shares, shutdown is stalled by the fact that the OS shuts down the network interface, then attempts to unmount the networked drives. This causes stalls in the shutdown that can last minutes. I've managed to resolve the issue with this post.
However, I'm still having a problem on startup. The network isn't alive when it tries to mount my shares and the mount fails. If I manually mount the drives through a terminal after startup, it works fine. Now here's the oddity. If I reboot(and not cold start), the drives do mount properly, leading me to believe that reboot uses a different process order than startup. Is this true?
How might I get my startup to follow reboot's lead, where network is brought up prior to the drives being mounted?
thanks,
jsonAloof linux user #whatever.
I tested off the charts for MENSA. Unfortunately, it was off the wrong end of the chart.
- 10-19-2009 #2
Are you using Ubuntu's networkmanager?
I would guess that could be part of the problem. As far as I know, it starts with the desktop session, so anything requiring internet connectivity during the boot process is out of luck. You can switch to WICD, which should start up the network during the boot (at least it does for me on arch), or setup the network in /etc/network/interfaces
- 10-19-2009 #3
Look in your rc#.d directories. There you should see files starting with K## or S## K=Kill/stop S=Start. Just re-arrange the numbers after S to start the process in the order you need stated. Make sure your network is staring before you netfs/autofs. Lower numbers start first. Same thing with the shutdown process, rc6.d, make sure the netfs is shutting down before the network.
- 10-20-2009 #4
Hi there guys and thanks for the replies.
Lazy, I looked in my rc.d directories and didn't find netfs, but rc6.d seems to hold all of the file file unmounting commands as well as networking:
Is S31umountnfs.sh the one I need to move to rc.5d?K20kerneloops
S01linux-restricted-modules-common
S35networking
K25hwclock.sh
S10unattended-upgrades
S40umountfs
K50alsa-utils
S15wpa-ifupdown
S60umountroot
K74bluetooth
S20sendsigs
S90reboot
K99laptop-mode
S30urandom
README
S31umountnfs.sh
Thanks for your thoughts,
jsonAloof linux user #whatever.
I tested off the charts for MENSA. Unfortunately, it was off the wrong end of the chart.
- 10-20-2009 #5
Also, for clarification, does startup use this list as well, just in reverse order?
Aloof linux user #whatever.
I tested off the charts for MENSA. Unfortunately, it was off the wrong end of the chart.
- 10-20-2009 #6
- 10-20-2009 #7
README
S20speech-dispatcher
S90binfmt-support
S01policykit
S25bluetooth
S99acpi-support
S10apmd
S50cups
S99grub-common
S10sysklogd
S50pulseaudio
S99laptop-mode
S11klogd
S50rsync
S99ondemand
S20dkms_autoinstaller
S50saned
S99rc.local
S20hotkey-setup
S70dns-clean
S99stop-readahead
S20kerneloops
S70pppd-dnsAloof linux user #whatever.
I tested off the charts for MENSA. Unfortunately, it was off the wrong end of the chart.
- 10-20-2009 #8
Do not see where your network is being loaded. I don't know Ubuntu hopefully someone who knows Ubuntu better can help you with this. I guess all distros don't manage things the same way.
- 10-20-2009 #9
Thanks very much for taking a look at it Robert. I appreciate the effort!
Aloof linux user #whatever.
I tested off the charts for MENSA. Unfortunately, it was off the wrong end of the chart.
- 10-21-2009 #10
You might want to try on the Ubuntu above in Your Distro


Reply With Quote

