Sujet : long uptimes and mountd port
De : usenet.16 (at) *nospam* scottsonline.org.uk.invalid (Mike Scott)
Groupes : comp.unix.bsd.freebsd.miscDate : 05. Mar 2025, 09:39:26
Autres entêtes
Organisation : Scott family
Message-ID : <vq92ju$2baf9$3@dont-email.me>
User-Agent : Mozilla Thunderbird
Just a thought... I've just had to stop and restart an rpi-based server after an uptime of 454 days (not an issue with fbsd - we just had to shut the power off)
It restarted properly except dovecot didn't appear. Which raises a couple of questions:
1. When packages are upgraded, the program's not automatically restarted, and this can lead to an accumulation of issues that may only appear long after the upgrade is forgotten. Something like apt does restart the program, IIRC, which seems a much better idea.
2. Unhelpfully, dovecot didn't say what was up. 'service start dovecot' just exited quietly with status 89. Not helpful; only starting it manually with appropriate options did I get the error message.
3. The issue was actually with mountd, which had suddenly decided to use port 993/imaps. Weird!! At least it was easily fixed (-p 992).
But kudos for the uptime!
--
Mike Scott
Harlow, England