Running a Phantom process

attu · Post by **attu** » Wed Dec 12, 2007 2:42 pm

If a dsjob command is used from command line with nohup.

 nohup dsjob -run projct job &

what would be the impact if the unix session timesout?
Would it still run without a broken connection (81002).

Thanks

chulett · Post by **chulett** » Wed Dec 12, 2007 2:47 pm

There's no need for that. The dsjob command with none of the wait options already spawns a nohup'd background task.

attu · Post by **attu** » Wed Dec 12, 2007 2:55 pm

What if the session is timed out, and we get a broken connection error 81002, despite the fact the job completed successfully.

attu · Post by **attu** » Wed Dec 12, 2007 2:55 pm

What if the session is timed out, and we get a broken connection error 81002, despite the fact the job completed successfully.

chulett · Post by **chulett** » Wed Dec 12, 2007 3:03 pm

What about it? Is that why you are asking about nohup - you are getting timeout errors? The client can disconnect or timeout without effecting any of the background processes it started.

attu · Post by **attu** » Wed Dec 12, 2007 3:34 pm

Chulett, Thanks for replying promptly.

The job finishes successfully from the command line with following messages

Error 81002 waiting for job
status code 141

How do we determine and settle this warning.

Thanks

chulett · Post by **chulett** » Wed Dec 12, 2007 3:59 pm

Hmmm... search for the 81002 error turned up a few posts, inlcuding this one:

viewtopic.php?t=98411

As for the 141 error, you'll need to search the forums for that one as well, however I don't believe any conclusive reason was found for it. You'll probably need to take that to your official support provider for resolution if it sticks around as a problem.