Your message dated Thu, 15 May 2008 14:14:54 -0500
with message-id <[EMAIL PROTECTED]>
and subject line elog has been removed from Debian, closing #417595
has caused the Debian Bug report #417595,
regarding elog: init script shell variables should be sanitized
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
417595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417595
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: elog
Version: 2.6.3+r1764-1
Severity: minor

Many of the shell variables used in /etc/ini.d/elog are neither unset, nor
initialized to safe/reasonable defaults.  At best this is not very robust
and could lead to unintended consequences.

I'd recommend creating '/etc/default/elog' with the following line to
explicitly clear variables used in elogd's argument list:
  unset PIDFILE CONFFILE LOGBOOKDIR RESOURCEDIR PORT HOST VERBOSE

-- Brad

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (1000, 'testing'), (80, 'unstable'), (60, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.2
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages elog depends on:
ii  adduser                     3.102        Add and remove users and groups
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries

elog recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.6.3+r1764-1.1+rm

The elog package has been removed from Debian testing, unstable and
experimental, so I am now closing the remaining open bugs.

For more information about this package's removal, read
http://bugs.debian.org/472279 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

Kind regards,
--
Raphael Geissert


--- End Message ---

Reply via email to