nohup Stopped (SIGTTIN) problem

[Richard Lefebvre]

Hi all,

I've got the following problem with my AIX 4.3.2 any users who's shell
is ksh can't seem to be able to use nohup.

Wne the user does:

nohup xlC -g -c hello.C &

he gets:

Sending output to nohup.out
[1] 2548

and eventually:

[1] + Stopped (SIGTTIN) nohup xlC -g -c hello.C &

And hello.C is never compiled. What is in the setup that prevent nohup
from working properly. I have similar setup with other platforms and the
nohup seems to be working properly. Any hints on what could be wrong?

Rick

--
Richard Lefebvre, Sys-admin, CERCA, (514)369-5224 "Don't Panic"
Richard.Lefebvre(@AROBAS)cerca(.POINT)umontreal(.POINT)ca -- THGTTG
http://www.CERCA.UMontreal.CA/~rick/

[Tony Curtis]

>> On Fri, 06 Oct 2000 16:21:06 GMT,
>> ri...@asimov.CERCA.UMontreal.CA (Richard Lefebvre) said:

> [1] + Stopped (SIGTTIN) nohup xlC -g -c hello.C &

SIGTTIN indicates that something invoked through xlC is
trying to get input from the terminal.

/usr/include/sys/signal.h:
#define SIGTTIN 21
/* (@) background read attempted from control terminal*/

So it appears that xlC or one of its subprocesses is
waiting for some kind of user input. Does it complete
normally if you just run the compiler in the foreground?

** What's in the nohup.out file? **

Something to do with a license issue perhaps?

hth
t
--
Namaste!
And an "oogabooga" to you too!
-- Homer Simpson

[Norman Levin]

Tony Curtis wrote:
>
> >> On Fri, 06 Oct 2000 16:21:06 GMT,
> >> ri...@asimov.CERCA.UMontreal.CA (Richard Lefebvre) said:
>
> > [1] + Stopped (SIGTTIN) nohup xlC -g -c hello.C &
>
> SIGTTIN indicates that something invoked through xlC is
> trying to get input from the terminal.
>
> /usr/include/sys/signal.h:
> #define SIGTTIN 21
> /* (@) background read attempted from control terminal*/
>
> So it appears that xlC or one of its subprocesses is
> waiting for some kind of user input. Does it complete
> normally if you just run the compiler in the foreground?
>
> ** What's in the nohup.out file? **

Since a nohup'ed program is usually run when the user logs
off, stdout is typically redirected to a disk file. Since you
didn't do this, nohup did it for you. nohup.out contains
standard out.

It also appears that the program is expecting input. Maybe
a key press? have you tried redircting stdin to /dev/null?

>
> Something to do with a license issue perhaps?
>
> hth
> t
> --
> Namaste!
> And an "oogabooga" to you too!
> -- Homer Simpson

--
Norman Levin