Re: rc.subr: $pexp does not always contain daemon flags?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Tue, Jun 16, 2015 at 01:32:11PM +, nusenu wrote: Rebooting (without changing the config) solves the issue but is not really an option. I cannot reproduce here. I can reproduce it every (first) time on multiple fresh OpenBSD 5.7

Re: rc.subr: $pexp does not always contain daemon flags?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Rebooting (without changing the config) solves the issue but is not really an option. I cannot reproduce here. I can reproduce it every (first) time on multiple fresh OpenBSD 5.7 machines. I'm using ansible to automate the entire setup. I

Re: rc.subr: $pexp does not always contain daemon flags?

On Tue, Jun 16, 2015 at 01:32:11PM +, nusenu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Rebooting (without changing the config) solves the issue but is not really an option. I cannot reproduce here. I can reproduce it every (first) time on multiple fresh OpenBSD 5.7

Re: rc.subr: $pexp does not always contain daemon flags?

Rebooting (without changing the config) solves the issue but is not really an option. I cannot reproduce here. # /etc/rc.d/tor1921682553680 -d check doing _rc_parse_conf doing _rc_quirks tor1921682553680_flags -f /etc/tor/enabled/192.168.255.36_80.torrc doing _rc_read_runfile tor1921682553680

rc.subr: $pexp does not always contain daemon flags?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I'm having a problem with rc.subr to start two instances of a tor daemon with distinct daemon flags. I'm simply linking to /etc/rc.d/tor: ls -l /etc/rc.d/tor* /etc/rc.d/tor /etc/rc.d/tor192168028443 - /etc/rc.d/tor /etc/rc.d/tor19216802880 -