Yes, it is quite likely I changed the path.
Perhaps this should be a feature request instead - that if the path is
changed, that the directory is created ?
--
Lock directory not created in startup script
https://bugs.launchpad.net/bugs/84692
You received this bug notification because you are a
I think this would introduce complexity not required. /var/lock is a
standard directory and there should be no reason to change it unless a
specific need. If so, user should create the new location by himself,
it's a trivial task to accomplish.
--
Lock directory not created in startup script
/etc/apcupsd/apcupsd.conf has a line (line 72 in my copy)
# LOCKFILE path to lockfile
# Path for device lock file.
LOCKFILE /var/lock/apcupsd
I believe the lock is used to police access to the USB port to the UPS.
--
Lock directory not created in startup script
I checked Dapper config file and that is what I saw:
#LOCKFILE path to lockfile
# path for serial port lock file
LOCKFILE /var/lock
Could you please try to reinstall apcupsd?
--
Lock directory not created in startup script
https://bugs.launchpad.net/bugs/84692
You received this bug notification
Thank you for your bug report.
Could you please explain why /var/lock/apcupsd is required?
** Changed in: apcupsd (Ubuntu)
Status: New = Incomplete
--
Lock directory not created in startup script
https://bugs.launchpad.net/bugs/84692
You received this bug notification because you are a
