> I am not sure what thos openvpn calls do. If they fork something in the
> background, please be aware that systemd will kill that before
> proceeding.
Simply (re)create the tunnel device
> Maybe there's a race bewteen the openvpn and iptables commands in that
> the interfaces are not finished c
> There is no reason to lose valuable debugging information. All output
> is collected by systemd and is available via journal. Hiding it makes
> really no sense.
...
> Show quoted textThis is not a shell, and you cannot reference $PATH like
> this. Full
> content of the variable has to included i
I'm using an openvpn unit,
cat openvpn.service
[Unit]
Description=OpenVPN
After=syslog.target network.target
Before=openvpn.target
[Service]
PrivateTmp=true
Environment=PATH="/u
Hi,
> amavisd goes to 'background' when started – notice these parts of the
> log:
>
> > amavis[7130]: starting. /usr/local/sbin/amavisd at…
> > amavis[7131]: Net::Server: Process Backgrounded
> >
> > 7131 ?Ss 0:00 /usr/local/sbin/amavisd (master)
Well, that's obvious now that you po
Hi
THanks for the pointers. Using type=simple, and removing the unneeded
cmds, the unit for the 'smtpprox' perl daemon works exactly as expected!
As a next step, I'm attempting to extend the same method that just
worked to another perl-daemon -- the more complex 'amavisd'.
@ manual launch
I'm trying to launch a perl service using systemd.
The perl script is 'smtpprox'
(https://github.com/jnorell/smtpprox/blob/master/smtpprox)
The unit file I created is
cat /etc/systemd/system/smtpprox.service
[Unit]
Description=smtpprox
Requ
