We should keep logs for many purposes but we need them for just archiving. It'll be good to use the internal hard drive (an extra one other than the os drive) as a log disk just like the web proxy package using that device for proxying. We can take them any time we like just a backup file over ftp.
Gokalp
Re: Writing logs to the internal hard drive
If you do this the index gets larger and larger, and the performance of the router could be impacted if you view the log from the ROS.
Use a syslog server, it is optomized for this type of activity.
Use a syslog server, it is optomized for this type of activity.
Re: Writing logs to the internal hard drive
I don't want to use the logs in the routeros. I just want to write inside the device. With that, you won't be affected by any third party device failure and you can reach your archive any time to export out side.
We're already using syslog stuff but you need a second device other than routeros and you have to maintain it for availability.
Gokalp
We're already using syslog stuff but you need a second device other than routeros and you have to maintain it for availability.
Gokalp
Re: Writing logs to the internal hard drive
for now, only this is possible. limited to system drive:
Code: Select all
[normis@demo2.mt.lv] > log print file=ssss
[normis@demo2.mt.lv] > file pri
# NAME TYPE SIZE CREATION-TIME
0 console.rif .rif file 416620 oct/02/2007 14:29:44
1 supout.rif .rif file 384316 sep/25/2007 22:31:57
2 ssss.txt .txt file 9327 oct/04/2007 13:06:59
Re: Writing logs to the internal hard drive
Can an external one be used or is an internal hard drive preferred?
Re: Writing logs to the internal hard drive
it's changed now. you can now save it to any disk. just change the logging action "disk" to set the drive you want.
To log everything to file, add new log action:then make everything log using this new action:Code: Select all/system logging action add name=file target=disk disk-file-name=logyou can log only errors there by issuing command:Code: Select all/system logging action=fileThis will log into files log.0.txt and log.1.txt. You canCode: Select all/system logging topics=error action=file
specify maximum size of file in lines by specifying
disk-lines-per-file. <file>.0.txt is active file were new
logs are going to be appended and once it size will
reach maximum it will become <file>.1.txt, and new
empty <file>.0.txt will be created.
You can log into USB flashes or into MicroSD/CF (on
Routerboards) by specifying it’s directory name before
file name. For example, if you have accessable usb
flash as usb1 directory under /files, you should issue
following command:Code: Select all/system logging action add name=usb target=disk disk-file-name=usb1/log
Who is online
Users browsing this forum: ckonsultor, jollyrogr and 25 guests