It all depends on how the job environment is setup / initiated, and traditionally (from the SGE 5.2 days or even earlier?) there needs to have a check using "stty -g" before proceeding to run stty commands in a batch environment:
http://gridscheduler.sourceforge.net/howto/commonproblems.html#batch Of course, if we allocate a TTY for the batch job, then this message would disappear. But I believe over 95% of the batch jobs do not need a real TTY, and just allocate one so that we can make the warning message disappear would be overkill. Can you check if you have any stty commands in your csh startup / login scripts?? Rayson On Thu, Apr 28, 2011 at 6:49 PM, Mark Suhovecky <suhove...@nd.edu> wrote: > > I'm testing a new SGE6.2u5p1 installation. > > Our default shell around here is csh (don't ask me why- explaining will raise > my blood pressure). > When I submit csh scripts, the following appears in standard out: > > Warning: no access to tty (Bad file descriptor). > Thus no job control in this shell. > > I've been told that this is a warning csh gives when it's not interruptable. > > We don't get this error in our SGE6.2u1 environment, so I'm guessing there's > a way to > suppress this output, but danged if I can figure out how. > > Any pointers? > > Thanks, > > Mark > > > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users > _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
