Bug 195852 - mail/opensmtpd stops logging if syslogd is restarted
Summary: mail/opensmtpd stops logging if syslogd is restarted
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Dima Panov
Depends on:
Reported: 2014-12-10 14:49 UTC by Jason Mann
Modified: 2022-08-07 17:32 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (ashish)


Note You need to log in before you can comment on or make changes to this bug.
Description Jason Mann 2014-12-10 14:49:37 UTC
- Overview:

mail/opensmtpd logging stops working if syslogd is restarted, until opensmtpd is also restarted

- Steps to reproduce:

While opensmtpd is running and logging mail server activity, restart syslogd.

- Actual Results:

opensmtpd no longer logs through syslog.

- Expected Results:

opensmtpd should continue to log after syslog is restarted.

- Additional information:

Discussion with the software author and the FreeBSD port maintainer indicates that the root cause of this problem is that opensmtpd's processes open /dev/log before chrooting to /var/empty.

If syslogd is restarted, the file descriptors pointing at /dev/log are invalidated.  The opensmtpd processes try to reopen /dev/log, but as they are now chrooted to an empty directory, it is not found.
Comment 1 Bugzilla Automation freebsd_committer 2014-12-10 14:49:37 UTC
Auto-assigned to maintainer ashish@FreeBSD.org
Comment 2 Walter Schwarzenfeld freebsd_triage 2018-01-14 00:23:47 UTC
Maintainer feedback?
Comment 3 Dima Panov freebsd_committer 2018-01-14 04:07:05 UTC
(In reply to w.schwarzenfeld from comment #2)

Waiting for new, refactored opensmtpd release.
Comment 4 Walter Schwarzenfeld freebsd_triage 2018-01-14 04:15:01 UTC
Thanks of reply.
Comment 5 Rudolph 2021-01-25 14:51:58 UTC
Any news on this? On opensmtpd-6.8.0,1 I can confirm this bug still exists (FreeBSD 12.2).
Comment 6 Daniel Engberg freebsd_committer 2022-08-07 17:32:42 UTC
(In reply to Rudolph from comment #5)
Can you please submit a bug report upstream?