FANDOM


back to http://scratchpad.wikia.com/wiki/Sasecurity

I hope those figures are not correct as that could trash the CF card in no time. I have just about finished hacking/building a bandwith loging system for all clients connected to the node either via Autoauth or via Spashd. To do this I needed some storage space on the meshbox whereas to spool some of the cache files and temporary stuff. The simple way was to create my own ramdrive and put all the data in there. OK if the box goes down I loose up to 15minutes of data but that's really not to much of an issue. Saves blowing away a CF :) Now for a lot of the CFG files I could see no reason why a similar system could not be build whereas a ramdrive was created in order to hous the data that is regularly read and written. Not only that I was contemplating having other iterms and configs pulled from the network. Once the box is up and meshed I could see no reason why you could not have larger executable applications sitting on a central box with a hard drive then mount that drive and execute the application from there.

{{{

> >While working on writing scripts for monitoring  I ran "find /
> >-ctime -1" and got the following changed files.  I didn't bother 
> >listing the /proc files:-)
> >The list made me start wondering about how many writes a day go to 
> >the CF disk:
> >
> >
> >/etc/ACK (This equals 48 writes to the the CF each day correct?)
> >
> >a df -k /tmp yields:
> >Filesystem           1k-blocks      Used Available Use% Mounted on
> >-                            0         0         0   -  /tmp
> >
> >I've been trying to find out more about this output but I am coming
> >up blank so far.
> >Since it shows no file system, where does /tmp write to?  Is 
> it RAM I hope:-)
> 
> /tmp has to be written to RAM - there is a 32Mb CF card in the 
> machine, and if you try and download a new image to /, it will crap 
> out after about 5Mb, because the disk fills up. Downloading it to 
> /tmp works. Also, /tmp disappears on a reboot.
> 
> >The same is true for /var
> >I must confess some serious ignor

}}}

{{{

>While working on writing scripts for monitoring  I ran "find / 
>-ctime -1" and got the following changed files.  I didn't bother 
>listing the /proc files:-)
>The list made me start wondering about how many writes a day go to 
>the CF disk:
>
>
>/etc/ACK (This equals 48 writes to the the CF each day correct?)
>
>a df -k /tmp yields:
>Filesystem           1k-blocks      Used Available Use% Mounted on
>-                            0         0         0   -  /tmp
>
>I've been trying to find out more about this output but I am coming 
>up blank so far.
>Since it shows no file system, where does /tmp write to?  Is it RAM I 
hope:-)

/tmp has to be written to RAM - there is a 32Mb CF card in the 
machine, and if you try and download a new image to /, it will crap 
out after about 5Mb, because the disk fills up. Downloading it to 
/tmp works. Also, /tmp disappears on a reboot.

>The same is true for /var
>I must confess some serious ignorance here, they aren't getting 
>written to CF disk are they?  I always assumed not seeing how the 
>dhcp leases gets lost on re-boot

Same holds true for /var - you can download a 16Mb image to /var 
which wouldn't fit on the CF if it was being written there.

}}}


Links Edit

HardWare

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.