What's new

Syslog always going to JFFS now?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RocketJSquirrel

Senior Member
I apologize if I missed the memo on this. It seems the syslog on my 68U is now living in /jffs and not in /var/log, and there is no way to change this from the GUI.

I assume this is intentional so users can see prior logs which would get cleared on reboot if they lived in /var. Can we be sure the logs won't fill the router's memory?
 
I apologize if I missed the memo on this. It seems the syslog on my 68U is now living in /jffs and not in /var/log, and there is no way to change this from the GUI.

I assume this is intentional so users can see prior logs which would get cleared on reboot if they lived in /var. Can we be sure the logs won't fill the router's memory?
Logs are capped at 10meg as far as I know. Merry Christmas!
 
Suggestion: Change it to a directory, then install syslog-ng.
 
Suggestion: Change it to a directory, then install syslog-ng.
That would mean everyone would have to have Entware installed to get the syslog-ng working. Right?
 
Syslog is kept in /tmp
It is rotated between two logs at 256K. The most recent log is periodically copied to /jffs and on a reboot so it can be restored following the reboot. Been that way for a long time.

EDIT: Merlin just picked up a patch from me so that the log is also saved to /jffs when stopping the logger (prevented the possibility of losing a few log records on a reboot).
 
Last edited:
Maybe it changed in the later Merlin firmwares (I'm on John's fork) but AFAIK syslog was never stored in /var/log it was in /tmp. Then it was periodically copied to /jffs (unless you were running one of the very early MIPS routers).

The syslog rotates when it reaches a certain size (256kB on my router) and it only maintains one backup. So the maximum space occupied would be 512kB.

EDIT: Damn, John beat me to it. :D
 
EDIT: Damn, John beat me to it. :D
At least we gave the same answer! :)

EDIT: BTW, the patch I mentioned was actually a backport from my fork for a problem you found where we were losing log records when restarting wireless.
 
Thanks for the replies, guys. Glad you came up with the same answer. :rolleyes:
 
Once again I live and learn from the masters! :):)
 
EDIT: Merlin just picked up a patch from me so that the log is also saved to /jffs when stopping the logger (prevented the possibility of losing a few log records on a reboot).

And Asus made the backup location configurable in 45149. No idea if that code is finalized yet, I didn't test it. Check the "mainline" branch on Git, which contains the 45149 merge.
 
Logs are capped at 10meg as far as I know. Merry Christmas!

So it periodically writes the full 10meg syslog to jffs?

I’ve previously wondered on this but didn’t ask, how much quicker will JFFS memory wear out due to write operations from skynet diversion and syslog backups?
 
That would mean everyone would have to have Entware installed to get the syslog-ng working. Right?
Entware needs to be installed on the router, yes.
 
So it periodically writes the full 10meg syslog to jffs?

I’ve previously wondered on this but didn’t ask, how much quicker will JFFS memory wear out due to write operations from skynet diversion and syslog backups?
I was wrong on the 10 meg cap. @john9527 says the max is 512kb. No your jffs will not wear out, this has been discussed ad nauseam.:)
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top