Bug#670132: [Pkg-shadow-devel] Bug#670132: Useless ...terminated. messaged at the end of su invocation
On 05/20/2012 07:44 PM, Nicolas François wrote: Hello, I cannot use the strace. What is the return code from su? I though you were interested in the internal signal/syscall trace. The return code of su itself is 0: $ su -c id uid=0(root) gid=0(root) groups=0(root) ...terminated. $ echo $? 0 What is the failure with gcc-4.7. I will send the build failure later (I'm not on the correct machine right now). Can you limit the build to only su? Yes, su itself was building ok. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670132: [Pkg-shadow-devel] Bug#670132: Useless ...terminated. messaged at the end of su invocation
Hello, I cannot use the strace. What is the return code from su? What is the failure with gcc-4.7. Can you limit the build to only su? -- Nekral -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670132: [Pkg-shadow-devel] Bug#670132: Useless ...terminated. messaged at the end of su invocation
Hi, On Sat, May 19, 2012 at 03:03:05PM +0200, wav...@thregr.org wrote: On 18.05.2012 22:07, Nicolas François wrote: I tried to investigate a bit more. It seems that I get the message when the libpam-systemd (44-1) package is also installed. Looking at the pam_systemd manpage, it seems it can kill processes. Could su be one of them? Maybe this is also related to #667470. It could help if you could recompile su and log the signal received by catch_signals() in src/su.c Best Regards, -- Nekral -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
