Page 1 of 1

saving the system clock at shutdown

Posted: Mon Oct 03, 2011 5:21 am
by andriy85if
Linux Mint Debian 201109 on lap-top IBM R51. Buzzes on "saving the system clock" at shutdown. Shut down after 5 minutes waiting.

system updating didn't help... but I can specify what appears after long buzzing... that server on that address doesn't reply for 300 sec... in the capacity of server are addresses of my network discs... it's strange... how they connected with time

Re: saving the system clock at shutdown

Posted: Tue Oct 04, 2011 6:05 am
by andriy85if
in the file /etc/gdm/PostSession/Default wrote command umount -a to remove all network discs on shutting down. Everything is ok now!

Re: saving the system clock at shutdown

Posted: Thu Mar 08, 2012 5:21 pm
by on4aa
Thanks for this nice solution! That was a real time saver.
I ran in the same problem after having defined a CIFS mount to my NAS in the /etc/fstab on my LMDE XFCE notebook.
I only had to change gdm to gdm3, hence:

Code: Select all

gksu gedit /etc/gdm3/PostSession/Default
did the job for me.

Re: saving the system clock at shutdown

Posted: Mon May 07, 2012 7:49 pm
by MbopaakovI
Thanks a lot for this help.
I had also this problem on LMDE xfce (Eeepc 1005HA connected to a NAS at home) and I didn't know how to solve it. With the modification of the /etc/gdm3/PostSession/Default, the computer shutdown properly and in a short time.

Now my LMDE is perfect :-)

Re: saving the system clock at shutdown

Posted: Tue May 08, 2012 7:33 am
by proxima_centauri
* Moved to LMDE section

Re: saving the system clock at shutdown

Posted: Wed May 09, 2012 5:39 pm
by äxl
You should probably try to find the culprit instead of changing system files ...

Re: saving the system clock at shutdown

Posted: Sun Oct 14, 2012 9:33 am
by Golgot
For information, this trick was not working for me since last update.
I changed the added "umount -a" by "umount -l /mnt/nas " in /etc/mdm/PostSession/Default and now it's OK (up to the next update?)

It was already hard for me to find this workaround, so please feel free to find the culprit for me! :)