Are you using anything more complicated than mv/cp/ls etc? Are you sure
that the programs the shell script runs don't require manual input in
certain conditions (ie. cp file1 file2 when file2 exists.. do cp -f,
etc..)
If the programs have -f or --force options try that.. might fix
something.
Donncha.
Niall O Broin wrote:
>> Ideas please - I'm at my wit's end here. I have two scripts running on
> two Linux boxen. Box A runs a Perl script which processes some files and
> packages them up and copies them to box B. Box B runs a shell script which
> copies them to a third Linux box, where they are further processed, but
> that's not germane. My problem is that that both the Perl and shell script
> are designed to be run as daemons, so they have no user interaction (they
> do write log files). During debugging they're not yet started at bootup
> so I run them with nohup script & (nohup in case I shut down the session)
>> This works and I carry on working in the relevant shells. BUT every now and then
> I get the message
>> [1]+ Stopped (tty input) nohup script_name
>> before my shell prompt. To get back on track, I simply do an fg , hit enter a
> couple of times, press ^Z and then type bg again.
>> Bu I can't for the life of me see what's happening here - my script doesn't read
> from stdin, and I can't see that any of the programs it uses would do so either.
> All suggestions gratefully listeened too :-)
>
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
