Log files in /var/log, /dev file system

[michaelotto]

Hi MadJoker0815,

thanks for your fixes to the Roborock bots. One of the ideas behind the changes is, if I'm correct, to minimize file (write) access in order not to corrupt the file system.

Two issues here:

• the /var/log partition is not affected by the fixes, although there is quite some writing done here. Also, the default logrotate.d settings for these files are pretty relaxed, so the / partition could - over the course of several weeks - run full. I haven't observed this yet though, as my bot is quite new.
• why are the /dev/shm log files redirected to /dev/null? In my S50 bot, /dev is mounted as a devtmpfs file system, and if I understand this correctly, this is a ram disk file system, so these files, however heavily they're modified, should never corrupt the file system.

-- Michael

[MadJoker0815]

Hi michaelotto,

Thanks for your interest. You are right about the /var/log. But these are system logs you might want to have if something really goes wrong. /dev/shm files can fill up the tempfs and then cause a reboot. Thats why I linked them to /dev/null. It happened on my Gen1 twice, after linking them all was fine.

Hope this answers your questions.

-- Mad

[michaelotto]

Thanks for your answers. Unfortunately, the system loses the symlinks in /dev/shm from time to time (at least once a day) and starts them as regular files again. I haven't found why or when the system is doing that though.

That's why I don't symlink them any more but just delete them once a day (while watchdog is down).

[MadJoker0815]

You are right, the files do get recreated even if they are symlinked. I will also just remove them from now on while watchdoge is down. Thanks for the information.