Subj : Re: A37 linux .bsy file issue with mutil
To   : All
From : Ryan Fantus
Date : Thu Dec 14 2017 09:08 am

On Thursday, December 14, 2017 at 8:51:18 AM UTC-8, g00r00 wrote:
> RF> I noticed in the whats.new that there was some work done regarding
>  RF> failure to clean up those .bsy files - looks like in my case, things
>  RF> were made worse :( I am on linux, 64 bit, debian 9. Thanks for all the
>  RF> hard work!
>
> There was a typo in a file extension, but that change was made weeks ago and
> has been tested on FSX hub which is stupid active, so this probably isn't a
> general issue that everyone is seeing.  This means questions!
>
> How are you running fidopoll and mutil?  Are you doing it manually or with
> events or crontab?  Who owns the busy files?  Who owns fidopoll, mutil, etc?
> Do you use the MIS BINKP server or just fidopoll?

Hey g00r00, thanks for the reply :)

I'll answer inline:
How are you running fidopoll and mutil?
- I have events configured to run on semaphores for outbound mail, and on 
hourly jobs for attempting to get inbound mail. When I noticed I was no longer 
getting mail, I ran mutil from a shell, and that's where I noticed the .bsy 
issue.
Are you doing it manually or with events or crontab?
- Via events for outbound (semaphore detections) and hourly event jobs for 
inbound mail checking. I also did script it as a cronjob briefly, but clearly 
that's stuck as well :)
Who owns fidopoll, mutil, etc?
- BBS user recursively owns /mystic/*. It's worth mentioning I launch as the 
BBS user and not as root. Root has not touched anything at all here. I bind to 
non-exclusive ports so launching as a standard user is not a problem.
Who owns the busy files?
BBS user owns the busy files. If I do 'find /mystic -iname *.bsy' before 
running mutil, the only .bsy file is /mystic/sempaphore/mis2.bsy. If I look for 
..bsy files right after running mutil (when it gets stuck) I end up with the 
following .bsy files:
../semaphore/mutil.bsy
../semaphore/mis2.bsy
../echomail/out/cybernet.028/00c80001.bsy
../echomail/out/amiganet.027/03860000.bsy
../echomail/out/fidonet/00020064.bsy
../echomail/out/retronet.050/03060000.bsy
They are all owned by my BBS user. If I manually delete the .bsy files in the 
../echomail/out/*/ directories, the job completes. Then, the next time I run 
mutil, the exact same files are created.

It's worth mentioning that these are being created when I run mutil against my 
inbound mail .ini configuration file.

Do you use the MIS BINKP server or just fidopoll?
- I'm using mis2, but I'm using that as my binkp server.

Thanks g00r00!

--- SoupGate-Win32 v1.05
 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

.