RE: [leafnode-list] Will 2.x address these issues?

["Ben Holness" <ben@xxxxxxxxxxxxxxxxx>]

Bit of a kludge, but if this makes it blow up, simply create another
groupinfo file (e.g. groupinfo.home) with the groups that you want in it and
then run a shell script instead of fetchnews that does two things:

1. Run fetchnews
2. Copy groupinfo.home to groupinfo

Although this way you won't see what groups are coming in.

If you want to restrict access for your kids but still allow yourself full
access, you could run two copies of leafnode on two separate ports with two
separate spools and conf files. It's not too difficult :)

Ben

-----Original Message-----
From: Support [mailto:support@xxxxxxxxx]
Sent: 06 December 2001 22:48
To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [leafnode-list] Will 2.x address these issues?


OK, that's different. I don't know if this will work but you could
try going into /var/spool/news/leaf.node and creating a groupinfo
file that had just the groups of interest, then setting it read-only.

Presumably fetchnews would run and be unable to update this file with
the new groups - I don't know if it would blow up or not though.

Ted


-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list