SJS([EMAIL PROTECTED])@Mon, Mar 31, 2008 at 04:27:52PM -0700: > begin quoting Wade Curry as of Mon, Mar 31, 2008 at 04:09:07PM -0700: > > SJS([EMAIL PROTECTED])@Mon, Mar 31, 2008 at 03:45:49PM -0700: > [snip] <more snipped>
> > I wasn't aware of a shell builtin. A cursory scan of `man > > bash-builtins` didn't turn up anything about it. The man page for > > Oh, I default to *csh, not bash. I generally work under the assumption > that bash has copied most of tcsh anyway. > > My fault for not testing lesser shells. > > Zsh doesn't have it either. > > My fault not testing nominally superior shells. I confess, I knew that would bug you at least a little bit when I wrote it. ;-) I haven't noticed it in ksh either, but I don't have ksh handy atm. > > nohup, however, simply says that it makes the command ignore > > hang-up signals. The few times I've used it in the past, the > > redirections were left alone. Don't know if I've ever actually > > used it with a pipe, though. > > > > If the desire is to simply send STDOUT and STDERR to separate > > files, though, then you don't really need a pipe. > > > > nohup <command> [options] 1>filename.txt 2>otherfile.txt & > > Didn't we just cover streams in painful depth? You probably did. I probably deleted it because the subject line said something about school funding. :-D Probably. > > Something like the above usually does the trick for me. I guess I > > should specify /usr/bin/nohup in the future, though. > > I like the idea of using screen, as attaching to a running process > has appeal. I can kill it with ^C, for example, which makes me all > warm and fuzzy inside. I like the idea of using nohup, as attaching to a running process and killing it with ^C is too much hassle. I can kill it with "kill %1", for example. I'm warmer and fuzzier inside than you! Does it mean I'm sick if "kill"ing jobs gives me warm fuzzies? Wade Curry syntaxman -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
