elsen%kulesat.uucp@BLEKUL60.BITNET (Marc Elsen) (08/06/89)
I would like to know if the following NEWS command can be used WITHOUT
the /inquire flag :
NEWS> create newsgroup */server=SERVERNAME/protocol=decnet/inquire
When one removes the /inquire flag from the above command news
returns with :
'Newsgroup : * (NEWS.SYS Filter rejects news groupname)' ! ???
I would like to add this command in all 'CLIENT' newsskim procedures
so that they would automatically match their list of newsgroups
to that resident on the server.
/inquire however demands interactive response which of course isn't
available in batch.
p.s: Another suggestion for improvement : It would be nice if Ctrl-W (screen
refresh) also redefined the previously loaded keypad definitions.
Very handy if one is switching between terminal server sessions for
example.
Marc Elsen (System Manager/Software Engineer)
Katholieke Universiteit Leuven
Dep. E.S.A.T.
Kard. Mercierlaan 94
3030 HEVERLEE
Belgium
tel. 32(0)16220931(ext. 1080)
EMAIL : elsen@esat.kuleuven.ac.be
...!kulcs!kulesat!elsen (UUCP)
elsen%kulesat.uucp@blekul60 (BITNET)
psi%02062166012::elsen (PSI MAIL)
fritz@unocss.UUCP (Tim Russell) (08/07/89)
munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes: |perhaps the answer is to use a different verb for an automatic "catch-up" of a |client system to a particular server -- UPDATE springs to mind, but it is |already used - how about: | | UPDATE/CLIENT [/SERVER=node] [/PROTOCOL=protocol] | |which would create all newsgroups currently held on the server which are not |already defined on the client system?? I like this idea. It's one of the few things left that I'd really like to see. It was getting to the point that I was going to set up an NNTP server explicitly for the purpose of having our NNTP server send 'control' to it to create new groups automatically. Glad I won't have to. In the same 'new newsgroup' vein - we have a problem. The NEWREGISTER profile entry seems to be off by default, which seems terribly silly to me - our users are supposed to wade through 497 groups to find new ones? I'd like to see either a system-wide default profile (which would be preferable) or a default of /NEWREGISTER=* for that entry. |> p.s: Another suggestion for improvement : It would be nice if Ctrl-W (screen |> refresh) also redefined the previously loaded keypad definitions. |> Very handy if one is switching between terminal server sessions for |> example. | |I'm a bit wary of this one - C-W is meant to be fast, and a reload of the |keydefs would start slowing things down a bit... opinions? I don't like it either.. Maybe DEFINE/KEY/RELOAD or something? -- ---------------------------------+-------------------------------------------- Tim Russell, Computer Operator | Internet: russell@zeus.unl.edu Campus Computing | Bitnet: russell@unoma1 University of Nebraska at Omaha | UUCP: uunet!zeus.unl.edu!russell
gih900@UUNET.UU.NET (Geoff Huston) (08/08/89)
Marc Elsen writes --
> I would like to know if the following NEWS command can be used WITHOUT
> the /inquire flag :
>
> NEWS> create newsgroup */server=SERVERNAME/protocol=decnet/inquire
>
> When one removes the /inquire flag from the above command news
> returns with :
> 'Newsgroup : * (NEWS.SYS Filter rejects news groupname)' ! ???
The /INQUIRE name is used to flag the action of requesting the named server to
supply a list of all newsgroups, and the local system then requests the user if
the newsgroup should be created -
perhaps the answer is to use a different verb for an automatic "catch-up" of a
client system to a particular server -- UPDATE springs to mind, but it is
already used - how about:
UPDATE/CLIENT [/SERVER=node] [/PROTOCOL=protocol]
which would create all newsgroups currently held on the server which are not
already defined on the client system??
> p.s: Another suggestion for improvement : It would be nice if Ctrl-W (screen
> refresh) also redefined the previously loaded keypad definitions.
> Very handy if one is switching between terminal server sessions for
> example.
I'm a bit wary of this one - C-W is meant to be fast, and a reload of the
keydefs would start slowing things down a bit... opinions?
Geoff HustonSLOANE@kuhub.cc.ukans.edu (Bob Sloane) (08/08/89)
In article <8908061039.AA12213@kulesat.uucp>, Marc Elsen <elsen%kulesat.uucp@BLEKUL60.BITNET> writes: > I would like to know if the following NEWS command can be used WITHOUT > the /inquire flag : > > NEWS> create newsgroup */server=SERVERNAME/protocol=decnet/inquire I am a little confused about this. The /INQUIRE qualifier tells the CREATE command to get the names of the newsgroups to create from the remote server. If you don't specify /INQUIRE, then how would NEWS know the names of the groups? Perhaps your problem was that NEWS askes if each newsgroup should be created. This could be fixed by adding a /NOCONFIRM option to the create command. I agree, that would be nice. +-------------------+-------------------------------------+------------------+ | Bob Sloane \Internet: SLOANE@KUHUB.CC.UKANS.EDU/Anything I said is | | Computer Center \ BITNET: SLOANE@UKANVAX.BITNET / my opinion, not my | | University of Kansas\ AT&T: (913) 864-0444 / employer's. | +-----------------------+-----------------------------+----------------------+
gih900@UUNET.UU.NET (Geoff Huston) (08/09/89)
Tim Russell writes --
(quoting me somewhere here)
>|perhaps the answer is to use a different verb for an automatic "catch-up" of a
>|client system to a particular server -- UPDATE springs to mind, but it is
>|already used - how about:
>|
>| UPDATE/CLIENT [/SERVER=node] [/PROTOCOL=protocol]
>|
>|which would create all newsgroups currently held on the server which are not
>|already defined on the client system??
>
> I like this idea. It's one of the few things left that I'd really like to
>see. It was getting to the point that I was going to set up an NNTP server
>explicitly for the purpose of having our NNTP server send 'control' to it
>to create new groups automatically. Glad I won't have to.
I have now included UPDATE/CLIENT
- now that I look at the code this is equivalent to
NEWS> CREATE NEWSGROUP */SERVER=node/PROTOCOL=proto/INQUIRE/NOCONFIRM
but a hell of a lot less to type in!!
> In the same 'new newsgroup' vein - we have a problem. The NEWREGISTER
>profile entry seems to be off by default, which seems terribly silly to me -
>our users are supposed to wade through 497 groups to find new ones? I'd
>like to see either a system-wide default profile (which would be preferable)
>or a default of /NEWREGISTER=* for that entry.
I've had mixed responses on this one - There are two solutions - V5.9 now
supports a default NEWSRC file for first time users
(NEWS_MANAGER:NEWSRC.TEMPLATE) to allow a system initial default.
The second method is REG/SINCE=date which will pick out all newsgroups created
since a nominated date. A variant of this is REG/RECORD which records today's
date as a checkpoint. A subsequent call to REG/NEW will register you in all
newsgroups created since the recorded date, and also record the current date as
the new recorded date.
Geoff Huston
gih900@csc.anu.oz.auELSEN@esat.kuleuven.ac.be (Marc Elsen) (08/09/89)
In article <8908070818.AA17461@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) writes: > Marc Elsen writes -- > >> I would like to know if the following NEWS command can be used WITHOUT >> the /inquire flag : >> >> NEWS> create newsgroup */server=SERVERNAME/protocol=decnet/inquire >> >> When one removes the /inquire flag from the above command news >> returns with : >> 'Newsgroup : * (NEWS.SYS Filter rejects news groupname)' ! ??? > > > The /INQUIRE name is used to flag the action of requesting the named server to > supply a list of all newsgroups, and the local system then requests the user if > the newsgroup should be created - > > perhaps the answer is to use a different verb for an automatic "catch-up" of a > client system to a particular server -- UPDATE springs to mind, but it is > already used - how about: > > UPDATE/CLIENT [/SERVER=node] [/PROTOCOL=protocol] > > which would create all newsgroups currently held on the server which are not > already defined on the client system?? > This would be just fine for me ! -- Marc Elsen (System Manager/Software Engineer) Katholieke Universiteit Leuven Dep. E.S.A.T. Kard. Mercierlaan 94 3030 HEVERLEE Belgium tel. 32(0)16220931(ext. 1080) EMAIL : elsen@esat.kuleuven.ac.be ...!kulcs!kulesat!elsen (UUCP) elsen%kulesat.uucp@blekul60 (BITNET) psi%02062166012::elsen (PSI MAIL)
Marc.Elsen@tlsi.FIDONET.ORG (Marc Elsen) (08/12/89)
-- --+--+ +------+ Internet: Marc.Elsen@tlsi.FIDONET.ORG | | | | UUCP : ...!attctc!tlsi!Marc.Elsen | | +---+ | Note : TLSI is a FREE gateway for mail between | | | | : Usenet and Fidonet. For more informations + +----+---+ + : write to root@tlsi or attctc!tlsi!root TLSI: The Hard Drive Specialists - (214) 263-0707. We repair most brands.