Scripts locations

Discussion in 'Tomato Firmware' started by basmaf, Dec 6, 2012.

  1. basmaf

    basmaf Serious Server Member

    HI Guys,

    I was wondering if someone could point me to correct post :)
    Im looking for an overview of script locations startup/wanup etc..

    I know its there but I can't find it anymore.

  2. rs232

    rs232 Network Guru Member

    I guess you're looking for a place where to configure them?
    If so just go under:

  3. Bird333

    Bird333 Network Guru Member

    I think he's wanting to know where they are in the filesystem.
  4. rs232

    rs232 Network Guru Member

    ls -la /tmp/script_*
  5. koitsu

    koitsu Network Guru Member

    Those are where they are on the filesystem, however the actual scripts themselves (when adjusting them in the GUI, etc.) come from NVRAM variables; the firmware takes what's in the NVRAM variables, parses them, and dumps them into /tmp/script_* equivalents. /tmp doesn't get saved across a reboot, obviously, while NVRAM does.

    nvram show | egrep ^script_ will give you a list of most of them. The ones I'm familiar with are:

  6. rhester72

    rhester72 Network Guru Member

    Or you may be thinking of /opt/etc/config, with the *.fire, *.wanup, *.init, etc., etc. files...not sure exactly what you meant.

  7. koitsu

    koitsu Network Guru Member

    root@gw:/tmp# ls -l *script*
    -rwx------    1 root     root           536 Oct 23 01:12
    -rwx------    1 root     root           298 Oct 23 01:11
    These are what come from NVRAM variables.
  8. basmaf

    basmaf Serious Server Member

    Much thanks.

    This is what I was looking for.
    Im trying to port dd-wrt's optware the right way to tomato.

    I already noticed that profile in /opt/etc/ will cause strange behaviour.
    But im used to running dd-wrt and now installed shibby's FW on my E3200 to become familiar with tomato.

    Since i got a lot of request to support tomato on o.t.r.w take2 I want to give it a shot.

  9. koitsu

    koitsu Network Guru Member

    Don't bother with Optware on TomatoUSB. Just use Entware. I repeat: do not bother with Optware. Entware is maintained and the developers generally understand things correctly, while Optware is utter crap and thrown together.
  10. basmaf

    basmaf Serious Server Member

    It doesn't matter to me which package source I'll use,
    I want to implement the otrw idea. if it becomes etrw ;) thats fine with me.

    But are scripts in init.d executed on boot?
  11. koitsu

    koitsu Network Guru Member

    AFAIK, no.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice