I have confirmed this problem on dapper, and feisty herd5.
Same happens when starting the havp process via
sudo /etc/init.d/havp start:
Starting havp: Starting HAVP Version: 0.82
Filesystem not supporting mandatory locks!
On Linux, you need to mount filesystem with "-o mand"
Exiting..
I had to manually mount /var/run with the mand option, and then to
manually install clamav, and finally run sudo dpkg-reconfigure --force
havp (with running havp) in order to fix it.
** Changed in: Ubuntu
Sourcepackagename: None => havp
Status: Unconfirmed => Confirmed
** Description changed:
+ bug submission via https://answers.launchpad.net/ubuntu/+ticket/4318
+
[EMAIL PROTECTED]:~$ sudo apt-get upgrade
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up havp (0.79-1) ...
Starting havp: Starting HAVP Version: 0.79
Could not open lock testfile /var/run/havp/havp-bGmLnN: No such file or
directory
Maybe you need to: chown havp /var/run/havp
Exiting..
Exiting..
invoke-rc.d: initscript havp, action "start" failed.
dpkg: error processing havp (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
havp
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
havp does not start because of mandatory lock error
https://launchpad.net/bugs/94552
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
