Re: Central syslog server best practices?

From: John A. Martin (jamat_private)
Date: Sun Aug 12 2001 - 13:20:47 PDT

  • Next message: Brian Hatch: "Re: Central syslog server best practices?"

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    
    >>>>> "a" == andreaso 
    >>>>> "Re: Central syslog server best practices?"
    >>>>>  Sun, 12 Aug 2001 17:49:53 +0200 (CEST)
    
        a> You're probably logging into one big file on the syslog server,
        a> right?  If I'm not misstaken, at least Linux standard syslogd
        a> has/had some terrible performance problems when handling large
        a> log files.
    
    Here is an extract from the usual Linux syslog.conf(5)
    
       Regular File
           Typically messages are logged to real files.  The file has
           to be specified with full pathname, beginning with a slash
           ``/''.
    
           You  may  prefix  each  entry with the minus ``-'' sign to
           omit syncing the file after every logging.  Note that  you
           might  lose information if the system crashes right behind
           a write attempt.  Nevertheless this might  give  you  back
           some  performance, especially if you run programs that use
           logging in a very verbose manner.
    
    Another option might be to try RAID-0 (stripe).
    
    	jam
    
    -----BEGIN PGP SIGNATURE-----
    Comment: OpenPGP encrypted mail preferred.  See <http://www.gnupg.org/>
    
    iEYEARECAAYFAjt25LsACgkQUEvv1b/iXy+KIACcDn+tpyPJszKQPmHpTaxIJAgu
    uXAAnjXwxxpQh4TvUMXwcpFQ5Ur8/U4m
    =93JF
    -----END PGP SIGNATURE-----
    
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: loganalysis-unsubscribeat_private
    For additional commands, e-mail: loganalysis-helpat_private
    



    This archive was generated by hypermail 2b30 : Sun Aug 12 2001 - 13:56:58 PDT