1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Scripts Vs. Scheduler

Discussion in 'Tomato Firmware' started by yoda, Jun 20, 2009.

  1. yoda

    yoda Addicted to LI Member

    Hey, new guy here made the jump to open source firmware..
    with no problems at all.. is was really easy. I notice the two options in the left
    Scripts page and scheduler was wondering if anyone could tell me the difference between the two :biggrin:
  2. bogderpirat

    bogderpirat Network Guru Member

    scripts is for (shell) scripts that are executed upon system, firewall or wan startup, scheduler is if you want something to happen at a specific time.
  3. Planiwa

    Planiwa LI Guru Member

    Another difference is that in Version 1.25 the Scheduler does not work in a strictly compliant browser, such as Safari. The input fields are blocked. (Works in Opera.)
  4. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    What do you mean by "blocked"? Could you check the Javascript console (or wherever javascript errors show up) to see what the problem is?

    It works fine here in Firefox 3.5rc2.
  5. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    I just installed Safari and gave it a shot.

    It looks like a Safari bug, not a Tomato bug. If you resize the textfield (grab the lower right corner - a Safari feature), it magically becomes editable.
  6. Planiwa

    Planiwa LI Guru Member

    Works fine in Opera too. And Seamonkey.

    Does not work in Safari. Input forms start out 1 line high,
    Clicking on Enabled [] increases form height.
    Clicking inside form highlights border, but shows no cursor, and typed text does not display.

    No error messages.

    But after turning on debugging and messing about for a bit, the forms become responsive!?!

    Perhaps other Safari users might want to confirm that they (don't) have (same) problem?
  7. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    I confirmed the same for Safari in my last post, but, like I said, the textarea can be made editable by simply grabbing the text area and making it bigger. That seems to me to have to be a Safari bug. If there is something on the page that makes Safari think it shouldn't be editable, then it should stay that way regardless of dragging the size.

    The input forms starting out 1 line high when disabled is a feature that is present in all the browsers I tried.
  8. Planiwa

    Planiwa LI Guru Member

    (messages crossed, sorry.)

    Confirmed problem -- cannot input text -- in Safari Version 4.0.1

    Confirmed no problem on Safari Version 3.2.1

    Yup. Seems to be a problem in the new-fangled Safari 4.0.1
  9. TVTV

    TVTV LI Guru Member

    Eversince they went with the Intel CPUs, Apple are becoming more and more like Microsoft. :)
  10. Toastman

    Toastman Super Moderator Staff Member Member

    I personally like Safari, though v4 is way overdue for some bugfixes. But I have to confess that Firefox is the only browser I've tried that will correctly scale a complete window with Tomato QOS graphs down to a small box in the corner of my screen... [CTRL +/-]
  11. Planiwa

    Planiwa LI Guru Member

    Opera is very good at whole-window scaling.
  12. Toastman

    Toastman Super Moderator Staff Member Member

    Thanks, I'll try it again!

Share This Page