Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Mike Scott <usenet.16@scottsonline.org.uk.invalid>
Newsgroups: comp.mail.sendmail
Subject: long uptimes and mountd port
Date: Wed, 5 Mar 2025 08:37:14 +0000
Organization: Scott family
Lines: 25
Message-ID: <vq92fq$2baf9$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 05 Mar 2025 09:37:15 +0100 (CET)
Injection-Info: dont-email.me; posting-host="385fa135de28d33de973cfe2ec022361";
	logging-data="2468329"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX190hptxW2m1d7NsScQHg+zt34xmmVbyxJQ="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:6Jl0gYFBCuervNLXi30BIjduuPs=
Content-Language: en-US
Bytes: 1863

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