[arm-allstar] Hamvoip Operational Question

[Doug Crompton]

George,

   You are correct. Everything possible is written to a tmp file system
meaning RAM.  If you do a df at the linux prompt you will see this. The
entire system works out of RAM for writes after boot.  Here is a typical
server -

# df
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root        3762048 1738516   1812712  49% /
devtmpfs          443724       0    443724   0% /dev
tmpfs             477516       0    477516   0% /dev/shm
tmpfs             477516   48124    429392  11% /run
tmpfs             477516       0    477516   0% /sys/fs/cgroup
tmpfs             477516     284    477232   1% /tmp
tmpfs              51200    1508     49692   3% /var/log
/dev/mmcblk0p1    102182   31902     70280  32% /boot
/dev/sda1       59374732 3002524  53333028   6% /media/MS1
tmpfs              95504       0     95504   0% /run/user/0

So unless you create something that uses a vast amount of permanent storage
on the SD card and repetitively writes it, cards should last almost
indefinitely. I have cards that have been in service for as many as 5 years
or more.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Mon, May 18, 2020 at 1:07 PM "George via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I am curious about one area of Hamvoip operation. How often is something
> written to the SD Card (other than operator changes to the files or
> updates)?  For example, the logs, the list of stations currently on-air,
> etc.  Are these and other items in memory and not written out to the SD
> card?
> Thanks for any clarifications.
>
>
>
> Regards,
> George, NJ3HRedmond, Oregon USA
> DMR ID:  3141315
> AllStar Node:  49246EchoLink Node NJ3H-L:  3135
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org