Deutsch   English   Français   Italiano  
<vq92hr$2baf9$2@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

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: (retract - wrong group) Re: long uptimes and mountd port
Date: Wed, 5 Mar 2025 08:38:19 +0000
Organization: Scott family
Lines: 29
Message-ID: <vq92hr$2baf9$2@dont-email.me>
References: <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:38:19 +0100 (CET)
Injection-Info: dont-email.me; posting-host="385fa135de28d33de973cfe2ec022361";
	logging-data="2468329"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18j6s7RA8CqobWj7wP8gc5lwpFOtJNdTvA="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:3tDdiFmPoT1BJRFSgrQaSOnCKI4=
In-Reply-To: <vq92fq$2baf9$1@dont-email.me>
Content-Language: en-US
Bytes: 2092

Sorry -- wrong group!!!!

On 05/03/2025 08:37, Mike Scott wrote:
> 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