Bug#438554: pidentd: Errors writing pid file

2007-08-18 Thread Frans Pop
Note that on new installations the directory /var/run/identd is also no 
longer created.

As the /etc/inetd file still specifies that the service should be run as 
user 'identd' and as that user still _is_ being created, it still seems to 
me that this directory should be created and used.


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



Bug#438554: pidentd: Errors writing pid file

2007-08-17 Thread Frans Pop
Package: pidentd
Version: 3.0.19.ds1-3
Severity: serious

In my logs I noticed:
identd[8496]: s_open(/var/run/identd.pid, O_WRONLY): Permission denied

Which can be explained as it runs as identd and not as root.
Because of this, there is a special directory in /var/run:
$ ls -ld /var/run/identd/
drwxr-xr-x 2 identd nogroup 1024 2006-06-27 16:45 /var/run/identd/

But it seems that directory is no longer used, even though it looks like
it _was_ used in Etch.

/etc/identd.conf for Etch has:
# server:pid-file = /var/run/identd/identd.pid
while the same file for Sid has:
# server:pid-file = /var/run/identd.pid

Looks like this change of the default location of the pid file needs to
be reverted!

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-rc3 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pidentd depends on:
ii  adduser3.104 add and remove users and groups
ii  libc6  2.6.1-1   GNU C Library: Shared libraries
ii  libssl0.9.80.9.8e-6  SSL shared libraries
ii  netbase4.30  Basic TCP/IP networking system
ii  openbsd-inetd [inet-supers 0.20050402-6  The OpenBSD Internet Superserver
ii  passwd 1:4.0.18.1-11 change and administer password and
ii  update-inetd   4.27-0.5  inetd.conf updater

pidentd recommends no packages.

-- no debconf information


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