It depends on the size of the syslog.log file, not the number of lines. How large are your log files?I know the GPL version has not changed. I want to know why System Log is not cleaned up automatically.
It depends on the size of the syslog.log file, not the number of lines. How large are your log files?I know the GPL version has not changed. I want to know why System Log is not cleaned up automatically.
I saved a log on July 21 (388.7). It was 469 KB.It depends on the size of the syslog.log file, not the number of lines. How large are your log files?
The logfile is not pruned. It's instead rotated once it reaches 512 KB. That has always been the case (tho the max logsize might have changed at some point, I didn't keep track of it).@RMerlin Has the new version modified System Log? Thank you.
Which is still below the limit of 512 KB * 2 logfiles.I saved a log on July 21 (388.7). It was 469 KB.
Just now I saved a log file (388.8). It is 983 KB.
Thanks to RMerlin and @dave14305 for the reply. I'll keep watching the log file size.Which is still below the limit of 512 KB * 2 logfiles.
Can you show:I saved a log on July 21 (388.7). It was 469 KB.
Just now I saved a log file (388.8). It is 983 KB.
ps ww | grep syslog
ls -l /jffs/syslog.log* /tmp/syslog.log*
Can you show:
Code:ps ww | grep syslog ls -l /jffs/syslog.log* /tmp/syslog.log*
Morpheus@AX86Umor:/tmp/home/root# ps ww | grep syslog
1429 Morpheus 3424 S /sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 512 -l 7
27169 Morpheus 3424 S grep syslog
Morpheus@AX86Umor:/tmp/home/root# ls -l /jffs/syslog.log* /tmp/syslog.log*
-rw-rw-rw- 1 Morpheus root 485256 Jul 29 01:54 /jffs/syslog.log
-rw-rw-rw- 1 Morpheus root 524296 Jul 29 01:54 /jffs/syslog.log-1
-rw-rw-rw- 1 Morpheus root 485426 Jul 29 02:08 /tmp/syslog.log
-rw-rw-rw- 1 Morpheus root 524296 May 5 2018 /tmp/syslog.log-1
Morpheus@AX86Umor:/tmp/home/root#
Ok, that seems fine but it looks like you must have increased the log_size nvram variable from default 256 to 512?Code:Morpheus@AX86Umor:/tmp/home/root# ps ww | grep syslog 1429 Morpheus 3424 S /sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 512 -l 7 27169 Morpheus 3424 S grep syslog Morpheus@AX86Umor:/tmp/home/root# ls -l /jffs/syslog.log* /tmp/syslog.log* -rw-rw-rw- 1 Morpheus root 485256 Jul 29 01:54 /jffs/syslog.log -rw-rw-rw- 1 Morpheus root 524296 Jul 29 01:54 /jffs/syslog.log-1 -rw-rw-rw- 1 Morpheus root 485426 Jul 29 02:08 /tmp/syslog.log -rw-rw-rw- 1 Morpheus root 524296 May 5 2018 /tmp/syslog.log-1 Morpheus@AX86Umor:/tmp/home/root#
I'm confused why I have to modify the NVRAM variable. What will happen if I don't modify it? If I have to modify it, what should I do?Ok, that seems fine but it looks like you must have increased the log_size nvram variable from default 256 to 512?
EDIT: or it doubled the size based on available RAM.
Leave it be. The default is 256 but the firmware can increase it to 512 if you have enough memory.I'm confused why I have to modify the NVRAM variable. What will happen if I don't modify it? If I have to modify it, what should I do?
He's seeing a larger than 512 KB file because he's downloading from the webui. So, both files are concatenated together.Ok, that seems fine
Thanks. But even when I'm connected, it shows "no data connection". Kill switch is disabled.Read the changelog...
Its my Ethernet cable, sorry.Thanks. But even when I'm connected, it shows "no data connection". Kill switch is disabled.
Interesting issue I have. To be able to get my vpn client working, as I see as correct. I have to redirect all traffic through the vpn director, then I change it to redirect yes (all). It then works correctly, however when it reboots I have to change to redirect all through vpn director, then change it redirect yes (all), then it starts working again.
Note: when it redirect traffic through vpn director, I am assigned my vpn provider ip, however my ISP ip is what visible, when I check to see what is visible dns leak testing.
the images are after restart and my current settings. syslog after restart
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!