home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!caen!uwm.edu!fps.mcw.edu!brodie
- From: brodie@fps.mcw.edu
- Newsgroups: news.software.nntp
- Subject: (INN) expire and history permissions. help..?
- Message-ID: <1992Nov5.111724.706@fps.mcw.edu>
- Date: 5 Nov 92 11:17:24 CST
- Organization: Medical College of Wisconsin, Milwaukee, WI
- Lines: 38
-
- Here's a good question for the ol' INN experts out there. I seem
- to have a majority of the bugs worked out (i.e, I can NNTP back
- and forth!). However, locally, on the server, there's a nasty one....
-
- I have problems with expire. If I run "expire" as root, then I
- end up with my history files in a permission mess (all get chowned
- to be owned by root), and innd dies. (can't read the history file,
- since it's EXPECTING it to be owned by news, not root).
-
- No matter what file protection/etc I use for the history files, expire
- seems to trash whatever I've set and cause everything to die.
-
- The second alternative (which makes better sense to me anyway) is to
- run expire as 'news', not 'root'. When I try this, I get the following
- error:
-
- cannot open history.n in "w" mode, Permission denied.
-
- ....and after that, innd is permanently 'reserved'. In this case,
- none of the expire stuff gets done either.
- [and ALL the news hierarchy is owned by "news"]
-
- So, if I run expire as root, I'm hosed. If I run it as news, I'm hosed.
-
- help.....?
-
-
- --
- Kent C. Brodie - Sr. Systems & Network Manager InterNet: brodie@fps.mcw.edu
- Faculty Physicians & Surgeons uucpNet: fps.mcw.edu!brodie
- Medical College of Wisconsin MaBellNet: +1 414 266 5080
-
- begin 700 sig.file
- M+BYW:&%T(&1I9"!Y;W4@97AP96-T(&9O<B!A('1W;RUL:6YE('5U96YC;V1E
- ?9"!F:6QE+"!A(&-O;&]R('!I8W1U<F4_(" Z+2D@("UL
-
- end
-
-