Implementing a $ cat /usr/sbin/nodm #!/bin/sh strace $0.real 2> /tmp/ere
reveals time(NULL) = 1310476722 send(3, "<83>Jul 12 21:18:42 nodm[1632]: "..., 72, MSG_NOSIGNAL) = 72 rt_sigprocmask(SIG_SETMASK, ~[KILL STOP RTMIN RT_1], NULL, 8) = 0 waitpid(1633, 0xbfcc4f68, WNOHANG) = 0 time(NULL) = 1310476722 send(3, "<85>Jul 12 21:18:42 nodm[1632]: "..., 69, MSG_NOSIGNAL) = 69 kill(1633, SIGTERM) = 0 kill(1633, SIGCONT) = 0 from which we see /var/log/auth.log Jul 12 21:18:37 jidanni2 nodm[1632]: starting nodm Jul 12 21:18:42 jidanni2 nodm[1632]: X server did not respond after 5 seconds Jul 12 21:18:42 jidanni2 nodm[1632]: sending X server 1633 the TERM signal from which we conclude maybe my hardware is not as fast as Enrico's. Fortunately there is a way for the average home user to try six seconds instead of five. What is it? Thanks. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
