Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.6 Snow Leopard > Discussions
This discussion is archived
2443 Views 7 Replies Latest reply: Jan 12, 2010 1:40 PM by Charlie2k
Currently Being ModeratedDec 2, 2009 4:33 PM (in response to Adam A. Lang)Tried moving any ~/.screenrc out of the way temporarily; for testing?
Currently Being ModeratedDec 2, 2009 6:10 PM (in response to MrHoffman)Good idea, but I've never used a .screenrc.PowerMac G4 Cube, Mac OS X (10.3.x)
Currently Being ModeratedDec 3, 2009 9:47 AM (in response to MrHoffman)I'm not sure what you mean. Does screen open a port or something?Mac Mini, Mac OS X (10.6.2), Snow Leopard Server
Currently Being ModeratedDec 3, 2009 10:32 AM (in response to Adam A. Lang)
I'm not sure what you mean. Does screen open a port or something?
The internal implementations of both screen and ssh are a little funky, so trying to swap out the piece that you can here (ssh) for the piece that you want (screen) might show if the two tools somehow interfere. Rather than connecting to the box via ssh, (and strictly as a test) try connecting to the box via telnet. I use screen fairly regularly from the local box or via VPN, but I seldom ssh into the box running screen.
Currently Being ModeratedDec 5, 2009 10:18 PM (in response to MrHoffman)Fair enough. When I get a chance, I'll plug a monitor and keyboard into the server and try it from the console.Mac Mini, Mac OS X (10.6.2), Snow Leopard Server
Currently Being ModeratedJan 12, 2010 1:40 PM (in response to Adam A. Lang)I have the same problem.
'screen' runs ok when run from terminal, but not if I ssh into my machine and run it. It just freezes and I have to ctrl-z and kill it.
This bugged me so much I cracked out the debugger.
Basically screen forks early on in its life, and the child process (the one being seen as a zombie) is dying at some code that looks like this:
if (vprocmgr_detach_fromconsole(0) != NULL)
errx(1, "can't detach from console");
The function call is I think Apple specific, but beyond that I don't know what the problem is.
CharlieMacbook Pro Unibody (Late 2008), Mac OS X (10.6.2)