emerrging baselayout-1.9.0 breaks openvpn init script: /etc/init.d/openvpn start * Starting openvpn for aline... Sat May 8 10:51:01 2004 0: In [CMD-LINE]:1: Error opening configuration file: aline/local.conf: No such file or directory (errno=2) Sat May 8 10:51:01 2004 1: Exiting [ !! ] * Starting openvpn for mai... Sat May 8 10:51:01 2004 0: In [CMD-LINE]:1: Error opening configuration file: mai/local.conf: No such file or directory (errno=2) Sat May 8 10:51:01 2004 1: Exiting [ !! ] but: openvpn --config /etc/openvpn/aline/local.conf --writepid /var/run/openvpn-aline.pid --daemon --cd /etc/openvpn/aline works very fine seems runscript has a bug ;) Reproducible: Always Steps to Reproduce: 1./etc/init.d/openvpn start 2. 3. Actual Results: must start openvpn manually Expected Results: working ;)
Created attachment 30989 [details, diff] start-stop-daemon.c.patch update to start-stop-daemon 1.10.20 by agriffis made 4 days ago is leading to this. when start-stop-daemon is not started with option --chdir it will be default chdir to / before starting the daemon. as openvpn is started with relative values for --config and --cd this will fail. solutions: 1. use the new --chdir option from start-stop-dameon to change into /etc/openvpn. requires sys-apps/baselayout-1.9.0 and therefore no real solution from my side 2. move the --cd option from openvpn to the front and let openvpn change into the right directory 3. use absolute values for --config and --cd 4. patch start-stop-daemon to not chdir to / by default my favourite is number 4 because when no --chdir options is specified, start-stop-daemon should not chdir anywhere. this is expected behaviour from my side. if someone wants to chdir to / he can easily add --chdir / to the command line options. see attached patch for start-stop-daemon.c to implement this. sven
patch work great thanks
Committed to rc-scripts cvs, this will be in baselayout-1.9.1
baselayout-1.9.1 is in portage and baselayout-1.9.0 is removed. Thanks again!
