egghelp/eggheads community

varibles help

2011-02-25T16:19:23-04:00

Ok "0 */2 * * *" seems to be working so far

I think what the problem is , is that the first * meens every minute so that would explain why "* */2 * * *" done the command every minute instead of every 2 hours.

Thanks
Gemster

Edit: Yes its working every 2 hours with "0 */2 * * *"

Statistics: Posted by Gemster — Fri Feb 25, 2011 4:19 pm

varibles help

2011-02-25T14:44:04-04:00

Ok willyw,

Testing 0 */2 * * * now to see if that works, if not ill test the "0 0,2,4,6,8,10,12,14,16,18,20,22 * * *".

I guess thats a 4 hour test lol.

Ill let u know if any of them work in 4 hours

Thanks
Gemster

Statistics: Posted by Gemster — Fri Feb 25, 2011 2:44 pm

varibles help

2011-02-25T14:16:46-04:00

...
Yes willyw it works with "0 * * * *" but what if i need it for every 2 hours or every 3 hours ?

Here:
http://www.linuxhelp.net/guides/cron/
it says

If you wanted to run a command every 2 hours you could enter in */2 for the hour field. This would run the specified command at 2am, 4am, 6am, 8am, 10am, 12pm, 2pm, and so on. An example of this type of entry would be:

0 */2 * * *

And if that doesn't work, I wonder...
what if you entered a list of specific hours?
"0 0,2,4,6,8,10,12,14,16,18,20,22 * * *"

Statistics: Posted by willyw — Fri Feb 25, 2011 2:16 pm

varibles help

2011-02-25T13:58:48-04:00

It can contain up to five fields: minute, hour, day, month, weekday; delimited by whitespace.
So the "* */1 * * *" should trigger once every hour, 24/7/365 (or 366). A 'every two hours' crontab mask will be: "* */2 * * *"

It dosent tho. Even if i do "* */2 * * *" or "* */3 * * *" it still triggers every minute as tho its ignoring the /1, /2 or /3.

Yes willyw it works with "0 * * * *" but what if i need it for every 2 hours or every 3 hours ?

Thanks
Gemster

Statistics: Posted by Gemster — Fri Feb 25, 2011 1:58 pm

varibles help

2011-02-25T13:39:58-04:00

...
Its very confusing but i guess once u get the hang of it, it gets easyer to understand.

I won't argue with that.

Try:
"0 * * * *"

Won't that make it run every hour, on the minute that ends in :00 ?
If you want to choose a different minute of the hour, just change that number.

Disclaimer:
I'm not saying that this is THE right way to do it. Perhaps someone else will be along...

In the meantime, try it, and let us know.

Statistics: Posted by willyw — Fri Feb 25, 2011 1:39 pm

varibles help

2011-02-25T12:13:30-04:00

It can contain up to five fields: minute, hour, day, month, weekday; delimited by whitespace.

So the "* */1 * * *" should trigger once every hour, 24/7/365 (or 366). A 'every two hours' crontab mask will be: "* */2 * * *"

Statistics: Posted by caesar — Fri Feb 25, 2011 12:13 pm

varibles help

2011-02-25T11:51:30-04:00

I had a look at them site you posted but i still get confused as they do say "* */1 * * *" every 1 hour

or
"* *1-24 * * *"

and for every 2 hours it be like this:

"* *0,2,4,6,8,10,12,14,16,18,20,22 * * *"

is this correct. Its very confusing but i guess once u get the hang of it, it gets easyer to understand.

Thanks
Gemster

Statistics: Posted by Gemster — Fri Feb 25, 2011 11:51 am

varibles help

2011-02-25T11:34:46-04:00

...
"* */1 * * *" makes it do it every 1 min not once an hour.

Google for
crontab
and find some examples/help on how to use crontab.

All you are looking for, is the syntax.
You'll find other specific info on crontab too.

From tcl-commands.doc:

All cron operators are supported. Please refer to the crontab
manual for their meanings.

Here's a few:
http://linux.about.com/od/commands/l/bl ... rontab.htm
http://ss64.com/bash/crontab.html
http://adminschoice.com/crontab-quick-reference

(Every time I use it, I have to go look it up too )

I hope this helps.

Statistics: Posted by willyw — Fri Feb 25, 2011 11:34 am

varibles help

2011-02-25T07:11:52-04:00

Thanks caesar,

It now works but i found another problem :/

"* */1 * * *" makes it do it every 1 min not once an hour.

Thanks
Gemster

Statistics: Posted by Gemster — Fri Feb 25, 2011 7:11 am

varibles help

2011-02-25T02:31:07-04:00

I think you have an older version of TCL, cos in version 8.5.8 that I have the 'nocase' option exist. Anyway, replace the:

Code:

switch -nocase -- [lindex [split $text] 0] {

with:

Code:

switch -- [string tolower [lindex [split $text] 0]] {

and should work just fine.

In the second code with the 'bind:check' proc I do a check if the bind exists or not, cos if it exists and you want to create it again, or delete something that doesn't exist will give you an error. I just covered all the possible errors.

Statistics: Posted by caesar — Fri Feb 25, 2011 2:31 am

varibles help

2011-02-24T20:52:35-04:00

Wow caesar lol,

Slow down

Im still learning rember. Anyways let me get the first code posted working then ill move onto your last version, By looking at the code i see it checks the var when u do on/off.

Anyways befor i test that code and learn that id like to learn the first 1 and get that sorted befor i move on

well, the first version i done what u sed but i still get errors:

Tcl error [pub:tssync]: bad option "-nocase": must be -exact, -glob, -regexp, or --

Thanks
Gemster

Statistics: Posted by Gemster — Thu Feb 24, 2011 8:52 pm

varibles help

2011-02-24T14:42:31-04:00

Oh snap.

You get that error because you are using your old bind instead of the one I should have included in my previous post.

Before the:

Code:

proc pub:tssync {nick uhost hand chan text} {

add:

Code:

bind pub * .tssync pub:tssync

and remove other code. I've made this change in my previous post too.

Edit: Here's a enhanced version, one that is bug free (do a .tssync on or off twice and see what happens)

Code:

bind pub - ".tssync" pub:tssyncproc pub:tssync {nick host hand chan text} {  if {![string match -nocase $chan "#opers"]} return   if {![isop $nick #opers]} {    putserv "PRIVMSG $chan :Sorry \00310$nick\003, you dont have access to use that command"    return  }  switch -nocase -- [lindex [split $text] 0] {    "on" {      if {![bind:check "cron:tssync"]} {        bind cron - "* */1 * * *" cron:tssync        putserv "PRIVMSG $chan :TSSync turned \0039\002ON\002\003 by \00310$nick\003."        } else {        putserv "PRIVMSG $chan :TSSync is already \0039\002OFF\002\003."      }    }    "off" {      if {[bind:check "cron:tssync"]} {        unbind cron - "* */1 * * *" cron:tssync        putserv "PRIVMSG $chan :TSSync turned \0034\002OFF\002\003 by \00310$nick\003."        } else {        putserv "PRIVMSG $chan :TSSync is already \0034\002OFF\002\003."      }    }    "check" {      if {[bind:check "cron:tssync"]} {        set status "\0039\002ON\002\003"        } else {        set status "\0034\002OFF\002\003"      }      putserv "PRIVMSG $chan :TSSync is currently $status"    }    default {      putserv "NOTICE $nick :Correct syntax is: \002.tssync on/off/check\002"    }  }}proc bind:check {name} {  set status 0  foreach {type flags command hits bind} [join [binds]] {    if {[string equal -nocase $bind $name]} {      set status 1      break    }  }  return $status}proc cron:tssync {min hour day month weekday} {  putserv "PRIVMSG OperServ :tssync"}

I took the liberty to make it work only in #opers channel. You should remove the 'if {![string match -nocase $chan "#opers"]} return' line if don't want this behavior.

Statistics: Posted by caesar — Thu Feb 24, 2011 2:42 pm

varibles help

2011-02-24T09:59:08-04:00

caesar, your code does not work :/

When i do ".tssync on" i get this error:

Tcl error [tssync]: invalid command name "tssync"

Thanks
Gemster

Statistics: Posted by Gemster — Thu Feb 24, 2011 9:59 am

varibles help

2011-02-19T10:32:28-04:00

Take time to read this and bookmark it :
http://www.peterre.info/characters.html

Bookmark it, because you'll want to return to it, and re-read it too.

How to write eggdrop scripts that won't choke on special characters

by "Peterre"

Statistics: Posted by willyw — Sat Feb 19, 2011 10:32 am

varibles help

2011-02-24T15:08:59-04:00

You should 'split' the $text and take what you need from it with 'lindex'

Code:

set text [lindex [split $text] 0]

if {[onchan $nick #opers] == 1 && [isop $nick #opers] == 1} {

there's no need to check bouth, stick with just the isop as it wil return 1 if that user is on the channel and has op, else will return 0.
Also, here's another tip:

Code:

if {$something} {  will do this part if $something is equal with 1}if {!$something} {  will do this part if $something is equal with 0}

if {$text == "on"} {

You should start using either [string tolower $text] or [string match -nocase $text "on"] (same thing for "off" and "check") as "ON" isn't the same thing as 'on' and the script won't work
I would replace:

Code:

if {$text != "on" && $text != "off" && $text != "check"} {  putquick "NOTICE $nick : syntax is .tssync on/off/check"}

with something easier to change:

Code:

set commands [list "on" "off" "check"]if {![lsearch -exact $commands $text]} {  putquick "NOTICE $nick : syntax is .tssync on/off/check"}

OR use 'switch -nocase -- $text' like i did on the other topic that would take care of other inputs for you.

Code:

switch -nocase -- [lindex [split $text] 0] {  "on" {    # on stuff here  }  "off" {    # off stuff here  }  "check" {    # check stuff here  }  default {    # any other command goes here  }}

Move the 'if' check that sends this message:

Code:

putmsg #opers "Sorry \00310$nick\003, you dont have access to use that command"

at top and return after like this:

Code:

if {![isop $nick "#opers"]} {   putserv "PRIVMSG #opers :Sorry \00310$nick\003, you dont have access to use that command"   return}

Here's my version of your code with 'switch':

Code:

bind pub - ".tssync" pub:tssyncproc pub:tssync {nick uhost hand chan text} {  global tss  if {![isop $nick "#opers"]} {    putserv "PRIVMSG $chan :Sorry \00310$nick\003, you dont have access to use that command"     return  }  switch -nocase -- [lindex [split $text] 0] {    "on" {      set tss "on"      putserv "PRIVMSG $chan :TSSync turned \0034\002ON\002\003 by \00310$nick\003."      bind cron - "* */1 * * *" cron:tssync    }    "off" {      set tss "off"      putserv "PRIVMSG $chan :TSSync turned \0034\002OFF\002\003 by \00310$nick\003."      unbind cron - "* */1 * * *" cron:tssync    }    "check" {      putserv "PRIVMSG $chan :TSSync is currently $tss"    }    default {      putserv "NOTICE $nick : syntax is .tssync on/off/check"    }  }}proc cron:tssync {min hour day month weekday} {  putserv "PRIVMSG OperServ :tssync"}

Edit: Fixed minor typos and added the missing bind.

Statistics: Posted by caesar — Sat Feb 19, 2011 4:53 am