man, 04.10.2004 kl. 15.49 skrev Colin Walters: > On Mon, 2004-10-04 at 15:35 +0200, Kyrre Ness Sjobak wrote: > > > Then, 2 minutes later, another user logs in, pulls up his/her floppy, > > and... the floppy is mounted. Cant get it umounted, and can't mount > > his/her floppy. Grr... > > Yeah, it's a perennial problem. I guess people are trying to solve it > with user-space proxy filesystems and the like. Not sure how mature > they are. > Sure. Think KDE does that. > > But what if all volumes that the user mounted when he/she was logged on, > > automatically got umounted when the user who mounted it logs out? That > > would solve it. > > Hmmm. The argument against that I guess is that the user could want it > to stay mounted for one of their cron jobs or something. Maybe that's > sufficiently obscure that we could ignore it. But it still doesn't > solve the case of a user just ejecting the disk before logout. > That is just to obscure. You dont run cron jobs on a client off removable media. You just dont do that. But shure, make it possible to turn back on if neccesary. > > About the "console" flag: would a user sitting on an XDMCP terminal be > > considered a console user or not? > > No. > Good. Then we can finaly make removable media mountable on our thin-client-server. (today only root can do that) > > How is it determined if he/she is a > > console user or not? > > Local Linux console login or local GDM. Sound good But what happens if you log out with "control-alt-backspace"? Iv'e seen prosesses survive that... (and i have a certain thin-client-server, which has people which logged on in august, even if they certainly isn't logged on today...)
