Hey,
sorry i was not aware, that /etc/nets.boot is no longer working for
autostarting a network. Had I read News.Debian.gz in the doc folder, I
would have known ;-).
Hi,
after boot:
root@oimel:/home/prisma# systemctl status tinc
● tinc.service - Tinc VPN
Loaded: loaded (/lib/systemd/system/tinc.service; enabled; vendor
preset: enabled)
Active: active (exited) since Sun 2017-03-12 13:39:25 CET; 8h ago
Main PID: 1275 (code=exited, status=0/SUCCESS)
T
Package: tinc
Version: 1.0.31-1
Severity: serious
I can confirm this bug. It is pretty anoying because it results in tinc
not beeing started on boot (Showstopper for servers). And it hasn't
changed with newer versions.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy
Hi,
> You can enable debugging in /etc/security/pam_mount.conf.xml. Then the
> commands being executed by pam_mount (and some more info) will be listed in
> auth.log.
Debug looks like that:
Jul 29 22:16:34 oimel login[3409]: pam_mount(pam_mount.c:306) saving
authtok for session code (authtok=0x
Package: libpam-mount
Version: 0.43-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Since the update to 0.43 libpam-mount works no longer. Login is not
possible, no error messages in /var/log/auth.log. It seems that the
mount processes are
5 matches
Mail list logo