If assp is running under systemd control - start and stop assp using systemd!
If assp is under systemd control, exit code 1 is returned - because assp is unable to detect
from where INT/TERM/KILL/... was sent. It is assumed that systemd will not restart assp, if it has
requested a service stop - in every other case it is assumed, that systemd will know what to do!
You can't use DB: for griplist - RTM!
assp uses the default BerkeleyDB file permission, which is -rw-rw-rw- (0666) on linux/nix
the file permission is not explicit defined at DB creation time by assp and never set to 0644 at any time.
I'm unable to reproduce this issue!
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Probably related to this error:
This file always seems to have wrong permissions after startup.
ASSP version 2.8.2(25098) (Perl 5.034000) (on linux)
Probably related to
useDB4griplistwhich i've enabled. Can i useDB:forgriplistoption instead, so it's using my mariadb server?Last edit: ViceIce 2025-05-21
If assp is running under systemd control - start and stop assp using systemd!
If assp is under systemd control, exit code 1 is returned - because assp is unable to detect
from where INT/TERM/KILL/... was sent. It is assumed that systemd will not restart assp, if it has
requested a service stop - in every other case it is assumed, that systemd will know what to do!
You can't use DB: for griplist - RTM!
assp uses the default BerkeleyDB file permission, which is -rw-rw-rw- (0666) on linux/nix
the file permission is not explicit defined at DB creation time by assp and never set to 0644 at any time.
I'm unable to reproduce this issue!
Thomas
ok, I configured
AsADaemontoyes - externally controlledand my service looks like this:is there something wrong with this? should i configure the user and group via the service file instead of assp options?
How can i tell assp to shutdown when not using the above kill method?