Just deleted all the old wood (fido areas) from my BBS, and this is
just a test fom my board. :)
Welcome back from Deadwood.
I used your instructions with SEAL and wrote a batch file to SEAL DROP
E.
Everything went good, used echofix.exe to fix Maximus, I might
have missed a few but I'll kill them ... I'll get'them easy!
I do that with SEAL also (MSGCTL/FILECTL).
Had to do a bit of echo cleanup here recently myself. I got
in the habit of using SEAL PAUSE to stop echoes for downed
nodes, so it would be easy to RESUME if they came back up.
none in the past year. Surprisingly, there were 40-50 that
met that criteria out of less than 300 total subscribed
locally or passthrough.
Had to do a bit of echo cleanup here recently myself. I got
in the habit of using SEAL PAUSE to stop echoes for downed
nodes, so it would be easy to RESUME if they came back up.
But they never did come back to Fidonet eh. Bummer!
Ya the backbone is quite a bit smaller, I also noticed the latest backbone.na isn't the same as what my uplinks feeding me. My uplink is feeding me areas /not/ listed on the latest backbone.na
systems (or not). Now that updates are showing up again,
I'm not even sure if I'm still pointed to it.
I turned "on" seal's auto add, there is quite a few echo areas being added/setup, I was surprised .. thats fer sure.
From the .NA or on the side? Might be time for me to take a
look again.
From the .NA or on the side? Might be time for me to take a
look again.
From the .NA or on the side? Might be time for me to take a
look again.
This is what seal deleted according to the latest backbone.na
It's a prety long list .....
!CHINESE Echo
12_STEPS Echo
3613TEST Echo
4DOS Echo
4DOS_TC Echo
First: Looking at the backbone.na that I have from 09/08/09
quite a few of the echoes that your SEAL deleted are listed
there. (??)
Second: What did you tell SEAL via command switches to have
it do this kind of "cleanup"? Or was it something in the
SEAL.ini that was set to enable this kind of action?
First: Looking at the backbone.na that I have from 09/08/09
quite a few of the echoes that your SEAL deleted are listed
there. (??)
Hmmmm.. Dam!
I used a old backbone.na file. Owell seal is set to "auto add"
areas.
Not like I have a ton of users anyhow. :(
Second: What did you tell SEAL via command switches to have
it do this kind of "cleanup"? Or was it something in the
SEAL.ini that was set to enable this kind of action?
Batch file.
SEAL386 DROP E !CHINESE
I used a old backbone.na file. Owell seal is set to "auto add"
areas. Not like I have a ton of users anyhow. :(
YOu could use backbone.dst and create the batch file
automagically using HORst's listmod, i.e.
SO, every time Ross sends out a backbone.dst you could do
this automatically and only nuke the areas contained in it.
YOu could use backbone.dst and create the batch file
automagically using HORst's listmod, i.e.
Have seen you tout LISTMOD quite a bit. Sounds like a decent
alternative to my routine of inserting specific characters in
prepend and append locations using the editor or commandline search-n-replace and then replacing the characters with the
appropriate strings.
SO, every time Ross sends out a backbone.dst you could do
this automatically and only nuke the areas contained in it.
My ritual here is a bit more elaborate also. I prefer to evaluate
the history in the area first before deciding whether to retain it
as an archive in spite of it's backbone status, or dump it. So I
usually
- make a backup copy of SQUISH.CFG if I'm expecting a small set of
changes or SEAL LIST to make a backup .NA of what's already locally configured if I'm expecting a bunch
- SEAL DESCRIBE against the current .NA with the -f (forced) switch
- examine SQUISH.CFG to see which areas lost their descriptions due
to not being found in current .NA
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,044 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 49:59:45 |
| Calls: | 236,098 |
| Files: | 60,370 |
| D/L today: |
18 files (36,596K bytes) |
| Messages: | 289,202 |