Nohup Issue on Slackware < 13.0

[lonsbio]

From ssade...@gmail.com on 2012-01-27T09:53:46Z

Information from user:

---

Bpipe depends on nohup. But the "nohup" command runs on the different
slackware versions (slackware 12.1) vs other Linux distros differently. The
"nohup" command is used to execute each section of the pipe script in the
background. If you edit the bpipe script in the bin/ directory and search
for "nohup" you'll see how it is used for bpipe.

The "nohup" command insists on having everything directed to a file (either
specified by "> filename" or by default it will go to a file "nohup.out") so
nothing gets sent to the terminal. Funny thing is this behavior is only
limited to slackware versions < 13.0.

If you edit the bpipe script, and add the following lines at line 184 (just
before the nohup line) and comment out the nohup line:

j=$$
touch .bpipe/logs/$j.log
java -classpath "$CP" -Dbpipe.pid=$j bpipe.Runner $TESTMODE $* 2>&1 &
disown

then you'll get the output to the screen and it will still run in the
background if you logout. I'm sure if we spend more time researching "nohup"
we'll find away to get it to display to stdout, but I'm not too well to do
that.

That being said, since you may be running complex, long jobs that won't
finish after a few seconds, you can just use the original bpipe script with
the "nohup" command as it is. The output will be appended in
bin/.bpipe/logs/$$.log which you can tail to see the progress output of
your pipe script.

Original issue: http://code.google.com/p/bpipe/issues/detail?id=1

[lonsbio]

From ssade...@gmail.com on 2012-01-26T16:57:23Z

Verified on Slackware 12.0 with Bpipe 0.1.4.

Fixed checked in / will be released in 0.1.5 (available shortly).

Status: Fixed
Labels: -Priority-Medium Priority-High