Package: fam
Version: 2.7.0-17.2+b1
Followup-For: Bug #483811
Dear Maintainer,
the segmentation fault is still there and the daemon is not restarted by the
systemd (which may overcome the problem temporarily).
>From the syslog:
Jul 6 17:24:34 XXXX famd[24040]: stat on
"/var/mail/virtmail/DOMAIN/USER/Maildir/./tmp/courier.lock" failed: No such
file or directory
Jul 6 17:24:40 XXXX kernel: [192404.960932] famd[24040]: segfault at 0 ip
000055ae8fcc0620 sp 00007fff791725f8 error 4 in famd[55ae8fcb1000+23000]
The same configuration was running fine with debian 8 stable, this problem
occurred after upgrade to debian 9.
Regards
Robert
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/12 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fam depends on:
ii libc6 2.24-11+deb9u1
ii libgcc1 1:6.3.0-18
ii libstdc++6 6.3.0-18
ii lsb-base 9.20161125
ii rpcbind [portmap] 0.2.3-0.6
ii update-inetd 4.44
fam recommends no packages.
fam suggests no packages.
-- debconf information excluded
