Thanks Mike. Picking unslung was simply the path of least resistance, I'm repurposing a machine that was already unslung and had everything else set up to my needs as a result.
I'm happy to go with the cheap drives/replace periodically approach vs. spending more time on this. Would still love a ssh/rsync remote backup recipe pointer for unslung, if one exists.
Thanks again.
--- In nslu2-linux@yahoogroups.com, Mike Westerhof <mwester@...> wrote:
>
> d0nv wrote:
> > I'm putting together a vacation home monitoring system for my in-laws based on an uNSLUng 6.8 slug. I have it now up and running producing graphs from the 1-wire sensors via temploggerd/RRDtool and displaying them via a separate instance of thttpd, so I can open just this one port to internet access. It is currently writing data to the USB memory stick for this purpose and I know this is going to wear it out quickly.
> >
> Not really. And they're cheap. I'll also mention that modern,
> good-quality USB flash devices do a good job of wear-leveling, so you
> can effectively increase the lifetime of the device if you only use a
> small percentage of the device's space. So, pick a 4GB unit, for
> example, for 12 USD at your local Walmart store, and expect it to last
> for years.
> > What I'd like to do is have it write to internal memory for web display and then periodically back the files up to the USB stick for persistence and also recovery of the data upon reboot.
> >
> > I've scoured the nslu2-linux.org site but can't seem to find a definitive answer on what amount of internal space is available and what file system path to use to access it for this purpose *on uNSLUng 6.8*. Is this info available?
> >
> Nope. Unfortunately, you picked the wrong firmware for that purpose --
> SlugOS would have given you the in-memory filesystem you want; it's not
> something that works out-of-the-box with Unslung. (I haven't checked,
> so I can't even say that you can find the stuff you need in the feeds to
> make it work at all with Unslung, frankly.)
> > Any/all tips appreciated. I'm coming up against deadline on this project (they leave shortly for several months, this is intended to cover them during that period).
> >
> > Believed applicable specifics on my system below. If these listings are both in the same units, I'm concerned there won't be enough space available...
> >
> > Thanks.
> >
> > # df -k
> > Filesystem 1k-blocks Used Available Use% Mounted on
> > rootfs 285603 179417 103240 63% /
> > /dev/sda1 6528 6344 184 97% /initrd
> > /dev/sda1 285603 179417 103240 63% /
> > /dev/sda1 285603 179417 103240 63% /share/flash/data
> > /dev/sda2 74843 4157 69913 6% /share/flash/conf
> >
> > Files and sizes that would need to be stored on internal memory for website display:
> >
> > # ls -l
> > -rw-r--r-- 1 website everyone 17327 Jan 4 21:52 280097A7020000tempe.png
> > -rw-r--r-- 1 website everyone 19061 Jan 5 00:25 2875BAA7020000tempe.png
> > -rw-r--r-- 1 website everyone 19206 Jan 5 00:25 28848BD5020000tempe.png
> > -rw-r--r-- 1 website everyone 19712 Jan 5 00:24 all_temperature.png
> > -rw-rw-rw- 1 root root 366912 Jan 5 00:25 temperature.rrd
> >
> >
> Small files. Put them on a modern USB flash device, and don't worry
> about it.
>
> -Mike (mwester)
>
No comments:
Post a Comment