Ok.
I know I did something wrong. I'm sure I'm an idiot, but I would appreciate someone telling me _why_ I'm an idiot...
Some FidoNet conferences got written to badareas.lst (because I hadn't subscribed to them I guess)
I ran scfg and imported badareas.lst, expecting those areas to be created in my msgbase.
Logged into the BBS and said "Yes" to new message scan. This is what I get:
FidoNet [ADM] Zone 1 Coordinator Contact Confere New: 0 of 0 FidoNet [ADM] Zone 1 Daily Nodelst process recei New: 0 of 1 FidoNet [ADM] Zone 1 Echo Routed Netmail Discuss New: 0 of 0 FidoNet [ADM] Zone One Echomail Coordinator New: 0 of 0 !ERROR opening /sbbs/data/subs/fidonet_brtestes
The sysop has been notified.
Did you run SCFG as a different user than the BBS runs as? Perhaps it's a permissions/ownership issue with the files created by SCFG.
I know I did something wrong. I'm sure I'm an idiot, but I wouldOk,
Re: Importing "badareas.lst"
By: Boondock to All on Tue May
04 2021 19:53:00
I know I did something wrong. I'm sure I'm an idiot, but I wouldOk,
replying to myself is bad, but I figured it out. For some reason importing the badareas.lst when running scfg from the command line as root set the owner and group to root instead of the bbsowner. Fixed that and it works now,
Boondock wrote to All <=-
I know I did something wrong. I'm sure I'm an idiot, but I would
Ok,
replying to myself is bad, but I figured it out. For some reason
importing the badareas.lst when running scfg from the command
line as root set the owner and group to root instead of the
bbsowner. Fixed that and it works now,
I know I did something wrong. I'm sure I'm an idiot, but I wouldI hope you learned something from this experience.
I also hope it's obvious what should have been learned. ;-)
Waaaaaay back I had just started a new job and we got a new AIX Box for production. Running a PICK database on Unix was new to all of us. Anyway, I made a classic mistake. We were all working as root (I don't think sudo had even been invented) and I
typed:
"rm -r /*&" instead of "rm -r \*&" to get rid of the files that were "xxx.yy*" Well, I'm sure those of you who understand have already winced so badly your face hurts ...
Boondock wrote to Gamgee <=-
Waaaaaay back I had just started a new job and we got a new AIX Box for production. Running a PICK database on Unix was new to all of us.
Anyway, I made a classic mistake. We were all working as root (I don't think sudo had even been invented) and I typed: "rm -r /*&" instead of
"rm -r \*&" to get rid of the files that were "xxx.yy*" Well, I'm sure those of you who understand have already winced so badly your face
hurts ...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 409 |
Nodes: | 16 (2 / 14) |
Uptime: | 73:25:53 |
Calls: | 8,576 |
Files: | 13,225 |
Messages: | 5,931,678 |