Package: inn2
Version: 2.4.3-1
Severity: normal

On startup of inn2 ovdb_monitor keeps it's inherited stdin open. 
Normally the inhereted stdin is /dev/console and that gets ovdb_monitor killed
when SAK is pressed.

Jul 17 20:03:45 gw kernel: SysRq : SAK
...
Jul 17 20:03:45 gw kernel: SAK: killed process 2883 (ovdb_monitor): fd#0 opened 
to the tty

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'experimental'), (400, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages inn2 depends on:
ii  cron                          3.0pl1-100 management of regular background p
ii  debconf [debconf-2.0]         1.5.13     Debian configuration management sy
ii  exim4                         4.67-7     meta-package to ease Exim MTA (v4)
ii  exim4-daemon-heavy [mail-tran 4.67-7     Exim MTA (v4) daemon with extended
ii  inn2-inews                    2.4.3-1    NNTP client news injector, from In
ii  libc6                         2.6-2      GNU C Library: Shared libraries
ii  libdb4.4                      4.4.20-8   Berkeley v4.4 Database Libraries [
ii  libpam0g                      0.79-4     Pluggable Authentication Modules l
ii  libperl5.8                    5.8.8-7    Shared Perl library
ii  libssl0.9.8                   0.9.8e-5   SSL shared libraries
ii  perl                          5.8.8-7    Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.8.8]     5.8.8-7    The Pathologically Eclectic Rubbis
ii  procps                        1:3.2.7-3  /proc file system utilities
ii  time                          1.7-21     The GNU time program for measuring

inn2 recommends no packages.

-- debconf information:
  inn2/preinst-upgrade1: false
  inn2/postinst-cannot-start:
  inn2/preinst-upgrade-largefiles: false


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to