RFC - tree quotas for Linux (2.4.12, ext2)
Quoted 3 lines · Mike Fedyk
Lets say that you have about 50GB of space, but you only want to allow 20GB for a certain tree (possibly mp3s), and you want to keep user ownerships of the files they contribute.
Then they just copy the mp3's wherever they want, and symlink them into the tree. No (meaningful) charge.
BTW, you get (almost exactly) the same effect by mounting a partition of 20Gb under /mp3
Signature · 2 lines
Horst von Brand [email protected] Casilla 9G, Vin~a del Mar, Chile +56 32 672616
Re: Swap
In reply to a message not in the archiveQuoted 44 lines · Nick LeRoy
Quoted 43 lines · Mike Fedyk
Quoted 27 lines · Steffen Persvold
Quoted 15 lines
Quoted 14 lines · Christopher Friesen
Quoted 12 lines · Richard B. Johnson
Quoted 6 lines · Wolfgang Rohdewald
Quoted 2 lines · J.A. Magallon
When a page is deleted for one executable (because we can re-read it from on-disk binary), it is discarded, not paged out.
What happens if the on-disk binary has changed since loading the program? -
It can't. That's the reason for
installand other methods of changing execututable files (mv exe-file exe-file.old ; cp newfile exe-file). The currently open, and possibly mapped file can be re-named, but it can't be overwritten.Quoted 5 lines
Quoted 3 lines
Actually, with NFS (and probably others) it can. Suppose I change the file on the server, and it's swapped out on a client that has it mounted. When it swaps back in, it can get the new information.
This sounds really dangerous... What about shared libraries ??
IIRC (if wrong flame...)
When you delete an open file, the entry is removed from the directory, but not unlinked until the file is closed. This is a standard UNIX semantic.
Quoted 6 lines
Now, if you have a set of processes with shared memory, and one closes, and another is created to replace, the new process will get the new libraries, or even new version of the process. This could/will bring down the entire set of processes.
Apps like samba come to mind...
*Any* time that you write to an executing executable, all bets are off. The most likely outcome is a big 'ol crash & burn. With a local FS, Unix prevents you from shooting yourself in the foot, but with NFS, fire away.. I've done it. It *does* let you, but...
Solution: Don't do that. Shut them all down, on all clients, upgrade the binaries, then restart the processes on the clients.
Quoted 8 lines
Quoted 6 lines
As far as the scenerio that you've described, I *think* that it would actually work. When the new process is fork()ed, it gets a copy of the file descriptors from it's parent, so the file is still open to it. If it the exec()s, the new image no longer has any real ties to it's parent (at least, not that are relevant to this).
What about processes with shared memory such as samba 2.0?
Cool, isn't it. Thinking of 1000 ways to crash apps. As long as the meaning of the bits and bytes in the shm segment does not change with a newer version of the app, you're safe. Upgrading in single-user modes makes things a lot safer (yes I too usually like to live dangerous....)
Signature · 10 lines
Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdam High Performance Computing Tel. +31 20 592 8008 Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams