Hey Folks, I have a newer enterprise linux box, and it's been inflicted with the systemd plague of creeping kludge; and /var/lock is now volatile.
I noticed the following was required after rpmbuild -ta'ing the vtun 303 tarball: # cat <<EOF> /etc/tmpfiles.d/vtund.conf d /run/lock/vtund 0755 root root - EOF # systemd-tmpfiles --create .. and that should allow the lock dir to exist; maybe even over reboots. If your box has I'll see about opening a bug so's it can get into a release. Other than that little tune-up, the 303 tarball seems to build only with minor griping. -- - bish p.s.: Relevant log bits Oct 20 13:29:03 ghostyghost vtund[s]: authentication[5986]: Can't create temp lock file /var/lock/vtund/me2you [root@ghostyghost ~]# ls -l /var/lock/vtund/ [root@ghostyghost ~]# rpm -V !$ rpm -V vtun S.5....T. c /etc/vtund.conf missing /var/lock/vtund [root@ghostyghost ~]# df /var/lock Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 3941272 8592 3932680 1% /run ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Vtun-Users mailing list Vtun-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vtun-users
