Florian Lohoff schreef: > On Mon, Nov 17, 2008 at 12:08:04PM +0100, Tim Dijkstra wrote: >> > 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. > > The point is you halt the application in the middle of saving and > continue to save on resume - Nothing the user can prevent - you are > stopping the whole system.
That seems a bit hard to trigger. You press save in your app and then you immediately try to suspend the system without waiting to see saving had finished? Still, I do not think that corruption on the server could be caused by this. Most likely your app would generate some error, in the worst case I think it would crash. >> 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. > > The point is that all other tools to suspend have this option and it is > used a lot. > > Suspend also takes down networking > (/usr/lib/pm-utils/sleep.d/10NetworkManager) whats the point in this? I > mean if you take down networking you also should take care of taking > down network filestems before disabling networking. This is inconsitent > behaviour ... That file is or should be part of NetworkManager. I must confess, I'm not using NetworkManager so I didn't notice it doing evil stuff. FWIW, I'm against bringing down network interfaces during suspend. Besides that, I thought that ifupdown already has some functionality that brings down networked filesystems if you bring down the interface. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
