On 2025/12/27 14:17, Otto Cooper wrote:
> 
> -------- Original Message --------
> On Saturday, 12/27/25 at 13:31 Stuart Henderson <[email protected]> wrote:
> 
> perhaps you had a bad file present when you were adding pexp in various 
> places but it's now cleaned up - if so then maybe you don't need the 
> additional pexp (which shouldn't be there)
> 
> 
> No, I copied and pasted /etc/rc.d/ from the .tgz package file to the email 
> above, so I am sure the content is identical to the original distribution 
> file.

The rc script in the current package is bad, it's been broken since the
last update. If you used it you'll have a wrong pexp in /var/run/rc.d.
If you fix the rc script you'll still have a wrong pexp in /var/run/rc.d
which would cause the behaviour you saw (the rc.d system uses the pexp
from when the daemon was *started* because in case you updated packages
and the string changed, however this breaks down if the package is
wrong).

On 2025/12/27 14:19, Otto Cooper wrote:
> 
> 
> 
> Sent from Proton Mail for Android.
> 
> -------- Original Message --------
> On Saturday, 12/27/25 at 13:31 Stuart Henderson <[email protected]> wrote:
> 
> > I have a script that does it all. Do you want me to post it here?
> 
> no need, thanks. doing a proper job requires 5 new ports to be written rather 
> than something via a script.
> 
> 
> I count more than 5 ports.

Lock::File
Log::Dispatchouli
Mail::BIMI
Mail::DataFeed::Abusix
Prometheus::Tiny::Shared

Reply via email to