On Sunday, August 21, 2005 at 01:57AM, Javier Fern?ndez-Sanguino Pe?a wrote:
On Sat, Aug 20, 2005 at 07:28:25PM -0400, Rick Friedman wrote: Oh, and BTW, the only change in -88 that might affect cron's behaviour is either SElinux support or the enabling of pam_limits.so. You might want to review /etc/security/limits.conf and see that it has sane values there just in case.
I don't have SElinux enabled and there's only comments in that file. I know this may not help much, but here's some bits from the core of the stripped binary. Loaded symbols for /lib/ld-linux.so.2 #0 0x400a4e69 in free () from /lib/tls/libc.so.6 (gdb) bt #0 0x400a4e69 in free () from /lib/tls/libc.so.6 #1 0x40033e6c in freecon () from /lib/libselinux.so.1 #2 0x0804af20 in ?? () #3 0x000a6575 in ?? () #4 0xbfefad18 in ?? () [ on and on ] #21 0x401739d4 in daylight () from /lib/tls/libc.so.6 [ and on some more ] In -88, u->scontext is set to NULL if get_security_context() fails (i think) and in free_user() there's a freecon() call on u->scontext but no NULL check. Maybe that's where the problem is? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
