Good question!
I have an update: everything works fine when started via systemd when I
change the unit file to Type=forking. Wondering how reproducible the
problem is on other platforms...
# /etc/systemd/system/backuppc.service
[Unit]
Description=BackupPC server
After=syslog.target local-fs.target
[Service]
Type=forking
User=backuppc
Group=backup
ExecStart=/usr/local/BackupPC/bin/BackupPC -d
RuntimeDirectory=BackupPC
PIDFile=/var/run/BackupPC/BackupPC.pid
KillSignal=SIGTERM
Restart=always
RestartSec=1
[Install]
WantedBy=multi-user.target
On Wed, Apr 12, 2017 at 12:47 PM Richard Shaw <[email protected]> wrote:
> Hmm... nothing jumping out at me there... I don't use SCGI so I'm not
> familiar with it but systemd works fine on my CentOS 7 and Fedora boxes...
>
> Now one thing to consider is that when systemd runs a process it's not in
> a shell and doesn't get a standard environment... Are there any environment
> variables that need to be defined?
>
> Thanks,
> Richard
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-users mailing list
> [email protected]
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
