Florian Lohoff schreef: > On Sat, Nov 15, 2008 at 05:25:19PM +0100, Michael Biebl wrote: >> Florian Lohoff wrote: >> > Package: pm-utils >> > Version: 1.1.2.4-1 >> > Severity: wishlist >> > >> > Hi, >> > please provide a sleep scriptlet to unmount network filesystems. I am >> > currently using this basically copied from /etc/init.d/umountnfs.sh >> > which does more than needed (unmounting sysfs etc) ... This needs to >> > be done before network manager is instructed to shut down networking >> > e.g. i used priority 07 ... >> >> Why is it necessary to unmount the network filesystems and shouldn't >> they mounted on resume again. > > Because typically your network filesystems will not be there after > resume. At least thats my typical use case - suspending at home - > going to work - resuming -
Well, that maybe typically for you;) > TCP based filesystems will even timeout > on the server as the tcp connection endpoint is gone and your tcp session > will timeout. The only sane state is to unmount all network based > filesystems on suspend. I never have had any problems with suspend and nfs (granted that is not TCP IIRC). We have machines with nfs home-dirs that do that daily here. > A sane way could be to refuse suspend if there are open files on the > network storage as the state could get severly garbled if suspending > with potentially dirty cache content or even resuming with some > expectation about the files state (which might have changed in the last > hours while we were suspended) so you could garble servers files on > resume because somebody else already appended to the file etc I do not have any profound knowledge about netword filesystems, but I do think this is highly unlikely. I mean, a network filesystem must be (by nature of going over an unreliable medium) tolerant to timeouts and clients comming back after being disconnected, etc. Also these filesystems are almost certainly developed with a multi-user environment in mind, so your argument about somebody else altering the file and causing corruption seems unlikely. Of course a user who resumes his machine could of course save his old file over a new one, but that wouldn't be different from somebody leaving his machine on for the night, comming back and doing the same. To conclude, I don't think thers is a technical reason to honour your whislist request in pm-utils. I do think there is probably a demant for something like this, but the best place to do something about it would be some higher level app. A level where people can interact and say yes/no or set a default, like gnome-volumne-manager or so. IIRC, it does already complain about mounted USD devices... grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
