Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-31 Thread Jan Rasche
Hello Steve, I'm sorry not really - but I may go after it later on. Steve Langasek wrote: Ok, this is exactly what it should show; this means that libpam0g detected cron as a service to be restarted, and attempted to restart it, but based on your log output cron didn't really get restarted for

Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-30 Thread Steve Langasek
On Thu, Aug 30, 2007 at 09:03:24PM +0200, Jan Rasche wrote: > Steve Langasek wrote: > >I'm afraid that this is exactly what is supposed to happen when you install > >the package non-interactively. > >Could you please send me the output of "debconf-show libpam0g" from this > >system? > Linux foo

Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-30 Thread Jan Rasche
Hi Steve, Steve Langasek wrote: I'm afraid that this is exactly what is supposed to happen when you install the package non-interactively. Could you please send me the output of "debconf-show libpam0g" from this system? Linux foo 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64 GNU

Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-30 Thread Steve Langasek
On Thu, Aug 30, 2007 at 05:20:47PM +0200, Jan Rasche wrote: > >Did you not get a debconf prompt when you upgraded libpam0g? Did you > >refuse > >to let the package restart cron for you? > Yes you are right! The issue was probably due to me running it in > autoupdate without getting notified du

Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-30 Thread Jan Rasche
Hi Steve, Thanks for your fast reply! Did you not get a debconf prompt when you upgraded libpam0g? Did you refuse to let the package restart cron for you? Yes you are right! The issue was probably due to me running it in autoupdate without getting notified during libpamg0 upgrade. So thi

Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-29 Thread Steve Langasek
On Wed, Aug 29, 2007 at 03:17:33PM +0200, Jan Rasche wrote: > I'm sorry but this Bug seems NOT fixed yet as I have 3 Servers (I know > this is not suggested ;-)) already on this version of PAM under todays > Debian GNU/Linux unstable having still this errors. > Aug 29 15:00:01 foo CRON[9890]: P

Bug#439845: NOT solved with pam 0.99.7.1-3

2007-08-29 Thread Jan Rasche
Hello Steve, I'm sorry but this Bug seems NOT fixed yet as I have 3 Servers (I know this is not suggested ;-)) already on this version of PAM under todays Debian GNU/Linux unstable having still this errors. Aug 29 15:00:01 foo CRON[9890]: PAM adding faulty module: /lib/security/pam_env.so