#312 -enable arg to all scripts

open
nobody
None
5
2012-06-18
2012-06-18
Avicennasis
No

It would be handy to have an optional -enable "Checkpage" option built into scripts by default - so that a bot can deactivated by non-admins, if so needed.

Discussion

  • Merlijn S. van Deen

    What is the behaviour you would want/expect when 'Checkpage' is enabled?

     
  • Avicennasis

    Avicennasis - 2012-06-18

    A simple boolean value - if the arg is used, read checkpage - if 'true', continue script - if false, stop and exit script.

    I know some of the scripts have a "enablePage" - but a lot of them don't.

     
  • Merlijn S. van Deen

    That doesn't tell me anything about what it should do. What is 'checkpage'? What should the bot do with it? When? What should it do in which case?

     
  • xqt

    xqt - 2012-06-18

    This behavior is not the same as blocking a bot by admins; it only prohibits the next start of the bot. So I am not sure if this is what you want to.

     
  • Avicennasis

    Avicennasis - 2012-06-19

    True, it is different then an admin stopping the bot via blocking, which of course would be instant. I was thinking more of implementations on cron - allowing any user to 'disable' the next run of a cronjob'd script until the BotOp is online/able to address a problem that may have arisen.

    (Alternatively, one could rewrite the -enable option to be checked every 10-25 pages, and so stop a bot from running even in 'mid-script'.)

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks