[Bug 381852] Re: xfs package: /var/run/xfs/xfs.pid or /var/run/xfs.pid ?

[Michael Vogt]

Thanks a lot firstofall for the patch Eric and sorry that we took so
long to review it.

I tested the package it on my natty system (maverick has the same
version) and the bug appears to be fixed by now. Unfortunately the
original bugreport does not have the version information of xfs.

Inspecting the init script it now says:

PIDDIR=/var/run/xfs
PIDFILE=$PIDDIR/xfs.pid

and also
set_up_pid_dir () {
  if [ ! -d "$PIDDIR" ] ; then
    mkdir $PIDDIR
    chown debian-xfs $PIDDIR
  fi
}

So that appears to be fine now. I will close the bug. Please reopen if I
overlooked something.

** Changed in: xfs (Ubuntu)
       Status: Incomplete => Fix Released

-- 
xfs package: /var/run/xfs/xfs.pid or /var/run/xfs.pid ?
https://bugs.launchpad.net/bugs/381852
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “xfs” package in Ubuntu: Fix Released

Bug description:
Binary package hint: xfs

After installing xfs on jaunty (apt-get install xfs), /etc/init.d/xfs (re)start said

xfs[17684]: cannot fdopen process ID file /var/run/xfs/xfs.pid for writing: No such file or directory
xfs[17684]: error opening process ID file /var/run/xfs/xfs.pid

But /etc/init.d/xfs is configured to use /var/run/xfs.pid (PIDFILE=/var/run/xfs.pid) ... and it started xfs daemon with this command line:
start-stop-daemon --start --quiet --pidfile /var/run/xfs.pid --exec /usr/bin/xfs -- -daemon

So it seems to be a bug ?