[GE users] Warning: no access to tty (Bad file descriptor).

Chris Dagdigian dag at sonsorol.org
Mon Jul 7 23:48:20 BST 2008

Not sure if this will actually help or hinder you but I've been  
spending a lot of time recently running SGE commands with the debug  
mode turned on and the level of detail in the output is extreme.  I've  
been running "qrsh hostname " debug level 4 and at that level it even  
tells me all about the files it is reading and the environment it is  
setting up. Downside is 1500 lines of text though! The verbose output  
*may* be chatty enough to identify the specific location of the tty  
stuff ..

To enable debugging:

Init the environment:

$   . $SGE_ROOT/util/dl.sh

Set a debug level:

$   dl 4

Run your command:

$  qrsh hostname

... and be prepared for a torrent of output of course.


On Jul 7, 2008, at 6:39 PM, Sean Davis wrote:

> I see in the FAQ that this error is related to having tty commands in
> the login scripts.  However, I cannot seem to find which of the
> scripts is causing the problem.  Is there a way to see what is going
> on to give me a hint where to look?  Between several shells,
> evaluation orders, and system login scripts, I wondered if anyone had
> any shortcuts besides hunting down every possible script?
> thanks,
> Sean

To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list