Log saved internally ( HyperWRT + WRT54G)

Discussion in 'HyperWRT Firmware' started by Tichi, Aug 23, 2005.

  1. Tichi

    Tichi Network Guru Member

    Is it possible to save log internally in the router instead of using
    syslog facility to other computer?

    should one run syslogdaemon on the router for this?

    In the administration/log one can see currently open connections only,
    isn'it it?
    how about the history nnn kBytes long?

    tnank you in advance for suggestions
  2. Tichi

    Tichi Network Guru Member

    figured out that syslogd run without parameters



    but how to restrict the size of this file?

    and what size is safe for HyperWRT?


    is anybody here?
  3. Tichi

    Tichi Network Guru Member


    syslogd [OPTION]...

    Linux system and kernel logging utility. Note that this version of syslogd ignores /etc/syslog.conf.


    -m MIN Minutes between MARK lines (default=20, 0=off)
    -n Run as a foreground process
    -O FILE Use an alternate log file (default=/var/log/messages)
    -S Make logging output smaller.
    -s SIZE Max size (KB) before rotate (default=200KB, 0=off)
    -b NUM Number of rotated logs to keep (default=1, max=99, 0=purge)
    -R HOST[:pORT] Log to IP or hostname on PORT (default PORT=514/UDP)
    -L Log locally and via network logging (default is network only)
    -C [size(KiB)] Log to a circular buffer (read the buffer using logread)


    # syslogd -s 40
    syslogd: illegal option -- s
    BusyBox v0.60.0 (2005.07.21-21:14+0000) multi-call binary

    Usage: syslogd [OPTION]...

    are not all these options implemented in Hyper WRT ?? !!

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice