writing bandwidth log to nvram/jffs2

Discussion in 'Tomato Firmware' started by nxmehta, May 9, 2007.

  1. nxmehta

    nxmehta LI Guru Member

    How bad of an idea is it to write the bandwidth log to nvram/jffs2? Will writing the log every day or every other day really cycle the flash memory too much (is that the concern here)? I keep seeing my bandwidth log cleared because of power outages or router reboots. I'd like to keep that data around, but I don't think that I can use CIFS since there are only laptops at my house that are not always home (no dedicated home server). So that leaves only NVRAM or JFFS2...
  2. roadkill

    roadkill Super Moderator Staff Member Member

  3. azeari

    azeari LI Guru Member

    well jffs2 does have write-wearing built in... still, that'll seriously shorten the lifespan or ur wrt
  4. nxmehta

    nxmehta LI Guru Member

    Ok, so jffs2/nvram is a bad idea... so here's my next question. If I set tomato to write the bandwidth log to CIFS every day, and the computer that it's supposed to write to is only connected during random times in the day, what will happen? Will it just fail to write when my computer is not around, or will it delay the write? At what time does it try the write?
  5. snwbdr

    snwbdr Network Guru Member

    You can set it to write every 1,2,3,4,5,6,7,8,9,12,24 hours or 2,3,4,5,6 days or once a week. Just set it up so it writes when a computer is on. Try every 24 hours. You can also back it up manually by hitting the backup button. Then put it in CIFS1 or 2 which ever you are using.
    edit: spelling
  6. roadkill

    roadkill Super Moderator Staff Member Member

  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