> > So sbbsecho is complaining of the following:
> >
> > Node (#:####/###) externally locked via: /sbbs/fido/out/09100069.bsy
> >
> > However, /sbbs/fido/out is empty. No bsy files or any files in it.
> Are you checking at the exact moment that SBBSecho is "complaining"? Checking
> some time later won't help.
Yes, it was spitting out the complaints while I kept an eye on the
directory. It was empty.
> The actual location shown/logged. Most likely, your mailer was connected with
> e node in question at the time of "complaint".
No. This was actually a new install that only had one node to connect
with, and the binkit event was turned off. No connections had been made
yet at the time. I was trying to pack a test message before making the
first connection.
The culprit, for future reference, was that the /sbbs/fido directory was
not owned by the bbs user. That was an operator error. Once I fixed that,
the message went away.
* SLMR 2.1a * I used to have a handle on life, then it broke.
---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
|