I have got a great idea to implement in the renice program. After trying to set
another priority to a compilation job on my box I realized that I had to type about
ten commands, reading the ps aux list every time to look up the process ID:s. Now, if
there would be a recursive function in it,
Paul Eggert [EMAIL PROTECTED] wrote:
JGraham [EMAIL PROTECTED] writes:
tell me you've never run a process that needed to run, then realized
that you had to log off?
I can't tell you that. OK, you're starting to convince me.
http://www.chiark.greenend.org.uk/~peterb/linux/interfereproc/
Tom,
What you describe is the behavior that
I would expect. mv(1) has never
been atomic when moving across filesystems;
it's only atomic when renaming
a single inode within a single filesystem.
Even in the single i-node on one filesystem
case it's not perfectly atomic,
at least under the
Jonathan Fors [EMAIL PROTECTED] writes:
I have got a great idea to implement in the renice program. After trying
to set another priority to a compilation job on my box I realized that I
had to type about ten commands, reading the ps aux list every time to look
up the process ID:s.
Try
JGraham [EMAIL PROTECTED] writes:
Come one, tell me you've never run a process that needed to run, then
realized that you had to log off?
You don't need nohup for that. Background processes will just continue
running after logout.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
Jim Meyering [EMAIL PROTECTED] writes:
So this would work like bash's `disown -h'?
I think it's stronger than disown -h. Not that I'm an expert, but my
impression is that disown -h merely arranges for the subprocess to
continue undisturbed even if Bash is HUPped. But Solaris 'nohup -p
27'
