Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1949 - VTUN daemon cannot write PID file
Attached to Project:
Arch Linux
Opened by BlueRaven (BlueRaven) - Friday, 31 December 2004, 00:30 GMT
Last edited by Dale Blount (dale) - Friday, 31 December 2004, 12:52 GMT
Opened by BlueRaven (BlueRaven) - Friday, 31 December 2004, 00:30 GMT
Last edited by Dale Blount (dale) - Friday, 31 December 2004, 12:52 GMT
|
DetailsHi, I recently installed VTun on one of my machines and noticed that the daemon complains about not being able to write its PID file.
This is the message I found in my /var/log/errors: vtund[1028]: Can't write PID file I had a closer look and discovered that the problem is due to an incorrect specification of --localstatedir in the ./configure step in the PKGBUILD: it should be /var instead of /var/run, because in the resulting Makefile the /run suffix is automatically added. I prepared a corrected PKGBUILD and am attaching the resulting patch. Please note that I also added a makedepends array, in order to make sure all the necessary tools for building VTun are installed (missing in the original PKGBUILD). I thought it was necessary, as I had some weird time figuring out all the needed dependencies. 
vtun.patch
(0.8 KiB)
|
This task depends upon