On Fri, Oct 13, 2006 at 11:08:27AM -0700, Adam Lazur wrote: > You may have to gdb as root to get a core because screen is setgid.
screen works perfectly if you run it as root - so thats no way to debug the problem. If I start as user in gdb, the following happened: (gdb) run Starting program: /usr/bin/screen (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912505525408 (LWP 2672)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Directory '/var/run/screen' must have mode 777. Program exited with code 01. But if I change /var/run/sreen to that mode: /usr/bin/screen Directory '/var/run/screen' must have mode 775. Strange... As another datapoint: on an opteron with libc6 2.3.2.ds1-22sarge3 and passwd 1:4.0.3-31sarge8 screen works, but not on two machines with the latest security updates. Any ideas ? Greetings Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
