I do the same but without nohup:
$ ksh
$ <command> [<parameters>] [>/dev/null] &
$ ^D

subshell does not issue SIGHUP on exit because the tty is still there. If
the program is started without output redirection the output goes to the
terminal even when you have left the subshell. On subshell exit the started
process becomes child of init (pid 1) so SIGHUP of parent shell does not
affect it. When you leave the parent shell the tty is closed so output of
the command is thrown away. I am a lazy guy so I would start it with only
"dsmc sched &" in a new aixterm or telnet session and later close both
shells.
Why nohup does not block SIGHUP is an old issue at it does exist before AIX
4.3.3 (sorry, I cannot remember was this since 4.3.2 or 4.3.0).


Zlatko Krastev
IT Consultant






Neil Schofield <Neil.Schofield AT YORKSHIREWATER.CO DOT UK> on 26.10.2001 
15:37:57
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: TSM scheduler stops by LOGOUT

Rene

I don't pretend to be an AIX expert but we had the same problem and found a
work-around was to start the scheduler in a sub-shell:

$ ksh
$ nohup /usr/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null 2>&1 &
[1]     47214
$ exit
$

Neil



The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682