[Dxspider-support] sh/lockout all

[Dirk Koopman G1TLH]

Whenever a new node appears they are automatically locked out. The 
reason for this was that we were having some problems with people doing 
stuff that we didn't like with rcmd and also just connecting randomly to 
other nodes.

This is why it is like this. What it means is that the sysop remains in 
control of whom he choses to let in.

Dirk

Keith Le Boutillier wrote:
> Hi All 
> 
> I just checked the command "sh/lockout all" and was surprised to see 589 callS in the list. I have only ever locked out one call here at GB7DXG-1 so the rest must have been propagated though the cluster network.
> I must admit that this was one command that I was not aware of maybe Dirk can fill us in on how this works.
> 
> 73 Keith GB7DXG-1
> 
> -----Original Message-----
> From: sysops-bounces at dxcluster.info [mailto:sysops-bounces at dxcluster.info] On Behalf Of Anthony(N2KI)
> Sent: 22 March 2009 10:46
> To: sysops at dxcluster.info
> Subject: Re: [sysops] Request to other SYSOPs
> 
> While on this subject, I happened to do a "sh/lockout all" and discovered a very long list of stations, of which I did not create.  Is this list propagated via upgrades?
> 
>  
> Anthony - N2KI
> 30MDG - 1187
>  www.n2ki.com
>  
>  
> 
> -----Original Message-----
> From: sysops-bounces at dxcluster.info [mailto:sysops-bounces at dxcluster.info]
> On Behalf Of Neal Campbell
> Sent: Saturday, March 21, 2009 7:51 PM
> To: Ian Maude
> Cc: sysops at dxcluster.info
> Subject: Re: [sysops] Request to other SYSOPs
> 
> I think any sysop wants to personally control the badspotters, etc without any list being propagated. I think almost all of the CC Cluster sysops badspotted/badannounced him 2 years ago so the sysops should do their best to do the same. Sysops using cluster sw without that capability should think about  migrating (IMHO).
> 
> Neal k3nc
> 
> 
> 
> On Sat, Mar 21, 2009 at 7:09 PM, Ian Maude <ian at gb7mbc.net> wrote:
>> Al - N1API wrote:
>>> I would like to ask the cluster SYSOPs if they would do something 
>>> about 5Z4FT / KI4LTH and his constant preaching all day long.  I know 
>>> in the
> world
>>> of radio clusters this would have never been condoned and he would 
>>> have
> been
>>> banished quickly.  Would you all please consider finding a way to 
>>> banish
> him
>>> from the telnet cluster, or at least cut off his announce features?  
>>> If
> the
>>> SYSOP where he feeds from can cut him out then that would help, if 
>>> not
> can
>>> the "system" be set to reject him?  His preaching does not seem to be 
>>> directed at anyone, and does not seem be on one particular subject at 
>>> a
> time
>>> but just things that seem to come to him and get thrown out as 
>>> mindless blabber.  Most  of the time, heck all of the time it does 
>>> not make any sense.
>> Hi Al,
>> Unfortunately, until *all* clusters start to run registration systems, 
>> this kind of thing will continue.  This idiot has long been set as a 
>> badspotter at gb7mbc and hb9drv-9 so nothing is seen of him here.  He 
>> also cannot log in to either and cause damage that way.
>>
>> The other thing is that he can log into a web cluster and do his 
>> damage from there without being visible to the network.  These are 
>> largely unpoliced and almost impossible to control.
>>
>> My advice to you is to runa  system with registration such as DXSpider 
>> and to set this guy as a badspotter.  Problem solved... at least for you.
>>
>> There have previously been debates as to whether a badspotter should 
>> be propagated through a node that has one set.  Maybe now is the time 
>> to re-open that debate?
>>
>>
>> 73 Ian
>>
>> --
>>
>> Ian J Maude, G0VGS
>> SysOp GB7MBC & HB9DRV-9 DX Clusters
>> Member RSGB, GQRP, FISTS
>> K2 #4044 |K3 #455
>> http://www.amateurradiotraining.org
>>
>>
>>
>> _______________________________________________
>> sysops mailing list
>> sysops at dxcluster.info
>> http://www.dxcluster.info/
>>
> 
> _______________________________________________
> sysops mailing list
> sysops at dxcluster.info
> http://www.dxcluster.info/
> 
> 
> _______________________________________________
> sysops mailing list
> sysops at dxcluster.info
> http://www.dxcluster.info/
> 
> 
> 
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>