| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 26 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 22:00:07 |
| Calls: | 484 |
| Calls today: | 1 |
| Files: | 1,074 |
| Messages: | 65,091 |
| Posted today: | 1 |
throw so many .bsy signals? It's typically with network 1,2 and b. Is
What do you mean bsy signals? Files left open or failure to connect.
BinkP connects on a different port than the bbs so shouldn't interfere.
While running network commands, the binaries create bsy files for the network they are in so we don't corrupt things by running network1 twice
for a given network at the same time
Yes this makes sense, however what would cause the .bsy files to not
remove after the connection and process is complete? I do not run the
hub but often need to log in to delete the *.bsy files in order to free
up packets stuck on the hub.
Not sure, are there any errors in the logs, maybe the network command crashes? also which of the bsy files are left?
Most often than not it is networkb.bsy, sometimes network1.bsy and network2.bsy. Those are the three most common. I'll double check the
logs to see what might be going I don't recall seeing anything out of
the ordinary.
RE: Re: .bsy signals with WWIV networking
BY: R3c0n #1 @126
Most often than not it is networkb.bsy, sometimes network1.bsy and network2.bsy. Those are the three most common. I'll double
check the
logs to see what might be going I don't recall seeing anything out of
the ordinary.
Sounds good, are you runnning networkb directly or is this from inside
of wwivd where it happens automatically?
rushfan
Not sure, are there any errors in the logs, maybe the network command crashes? also which of the bsy files are left?
I had the same issue, I fixed mine by backing up and then deleting the
*.bsy fil e and force a network connection from WFC.
Then I watched for any errors and addressed those, which mostly
consisted of the previous receive folder was not 'empty' and could
not completely remove it.
If you can run that network command with log level --v=4, maybe that'll
show the error happening from the filesystem level calls which are
casuing that file not to be removed. Warning it's a lot of noise.
Attaching that to an email to me at my wwivbbs.org emaila ddress and
filing an github issue or pinging me on here to take a look since I
don't chec internet email often would be helpful.
Thanks dude.
rushfan