ioFTPD SiteKill for ioFTPD 5.x

[FTPServerTools]

Well the exec is needed for ioftpd I read. If you execute an exe or so you need to put EXEC infront of it and for a tcl script you need to put TCL in front of it. Check your default ioftpd.ini and you'll see it there. All I did was follow that example.

[Jog]

i suppose that this script can be useful for someone.

it's a killidlers.tcl script for bots, u can use with ioBanana o dZSBot.

# A simple public killidlers.tcl by Jog
# works on ioFTPDSiteKill 2.0.4

bind pub -|- !SITENAMEkill pub_killidlers

proc pub_killidlers {nick uhost hand chan args} {
   set lcl_sitename "-SITENAME- \[KILL-IDLERS\] "

   if {[isop $nick $chan]} {
      putserv "PRIVMSG $chan :$lcl_sitename Kikking all idlers ..."
      set reply [exec -keepnewline -- "c:\\ioFTPD\\scripts\\SiteKill.exe" "user!=sitebot" "idletime>3" "service=FTP_Service"]
      set output "..."
      set msg [split $reply "\n"]
      foreach line $msg {
         putserv "PRIVMSG $nick :$lcl_sitename $line"
         if { [string first "Totally 0" $line ] > -1 } {
            putserv "PRIVMSG $chan :$lcl_sitename No idlers at the moment."
         } elseif { [string first "Totally" $line ] > -1 } {
            set pos [expr int([string first " connections" $line]-1)]
            set num_kiked [string range $line 8 $pos]
            putserv "PRIVMSG $chan :$lcl_sitename Kikked $num_kiked idlers."
         }
      }
   } else {
      putserv "PRIVMSG $chan :$lcl_sitename Only OPs can kill idlers."
   }
}

putlog "ioFTPDSiteKill 2.0.4 -Jog TCL- loaded"

this script catches the output of SiteKill and announce in the chan that is kikkink idlers and the number of users kiked, using private message sai the detailed kills to person who launched the command!

anyway u had to personalize the exec call and the sitename !!!

[MaistroX]

Sorry to have to say this, but latest version seems to crash, I my guess is that it relates to the "[Scheduler]" in ioFTPD.ini file !

My u can tell me IF there´s anything I could possibly change in ,y line to get it NOT to crash with this current version ?

my Line ->

"
KillIdlers = 0,5,10,15,20,25,30,35,40,45,50,55 * * * ..\scripts\ioFTPD_SiteKill\SiteKill.exe "idletime>120" service=FTP_Service service=FTP_Service2
"

THX.

[FTPServerTools]

Hmm I think it is because sitekill gives a reply back and io may not be able to handle that. A reply makes little use in the scheduler.
Maybe d1 can confirm this for me.
Please try redirecting the output to nul e.g.
KillIdlers = 0,5,10,15,20,25,30,35,40,45,50,55 * * * ..\scripts\SiteKill.exe groups!=SiTEOP groups!=nukers "idletime>120" service=FTP_Service >nul

That might do the trick. If not tell me and I'll add a new argument that stops giving output and would thus not crash accordingly. I think adding >nul should do the trick.

[MaistroX]

THX I´ll try

[MaistroX]

restarted, and still crashes !

[FTPServerTools]

2.0.5:Changed:Cosmetic update on total connections killed, the reasons were not seperated by a space.
Addedarameter to disable the output (needed when running from the scheduler)

If the very first parameter is debug then all kinds of debug info is given out. It helps me to resolve bugs.
Example:
sitekill debug "idle>120"
If the very first parameter is silent then there will be no output given whatsoever. This is needed when sitekill runs in the scheduler.
Example:
sitekill silent "idle>120"

How to use this command in ioFTPD 5.x? (not 5.0.x)
Lets say we for example want to kick all idle ftp users.

[Schedule]
KillIdlers = 0,5,10,15,20,25,30,35,40,45,50,55 * * * EXEC ..\scripts\SiteKill.exe silent "idletime>120" service=FTP_Service

or as a site command:
[Scripts]
KILL = EXEC ..\scripts\sitekill.exe

Use the same lines without the EXEC for ioFTPD 5.0.x

[FTPServerTools]

2.0.6:Added:transfer=idle/up/down/list seems I forgot that one

[SomeoneWhoCares_2]

dunno how long it stopped working but i am now getting these messages -> Error:Shared memory is not recognized by ioFTPD

[MidKnight]

trying to get it to kick last commands except for certain users, in this case flags with M

site kill action flags!=M =noop

[11:49:32] site kill flags!=M action =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Bad compare parameter in =noop
[11:49:32] 200-Totally 0 connections kicked, due to:flags!=M action =noop

[MidKnight]

using the following setup nothing happens at all, no one gets kicked, is there something i have missed?

im using v2.0.6 of sitekill

--------
[Scheduler]
###
# Scheduler
#
# Event = <minutes> <hours> <day of week> <day of month> Command
#
# Internal Commands:
#
# &Reset : Resets upload/download counters
# &Service_Update : Reloads devices and Restarts services, if bind ip of service has changed
#
Reset = 0 0 * * &Reset
Service_Update = 10,30,50 * * * &Service_Update
Rotate_Log = 0 0 * * EXEC ..\scripts\ioBanana.exe rotatelog
Day_Stats = 59 23 * * EXEC ..\scripts\ioBanana.exe daystats
KillIdlers = 0,5,10,15,20,25,30,35,40,45,50,55 * * * EXEC ..\scripts\SiteKill.exe silent "idletime>120" service=FTP_Service service=Local_FTP_Service

[MidKnight]

found why the scheduler wasn't working...... i am running io as a service

[FTPServerTools]

Hmm I didnt know that the scheduler then doesnt run. Be sure to have the 'interact with desktop' enabled and try again. It might run fine then, since some scripts give some responses back and thus they may not execute. Anyway I hope d1 reads this and checks it.

[darkone]

It's debugged throught out... (as someone complained that scheduler causes him crashes.. but it was something completely different)

[FTPServerTools]

The message is correct. Try:
site kill flags!=M action=noop

Be aware tho probably all users will have flags !=M you probably wanted to use:
site kill flags!=*M* action=noop

Oops that was a reply on an older question... Well whoever posted the question will know what it means.