Hi, David: yes, my server is running rsyslog 6.3.7-devel. Thanks for your suggestions - I will recompile rsyslog on my RHEL5 syslog-clients.
Have a nice weekend...:-) ! Br. ~maymann 2012/2/10 <[email protected]> > as far as I know, you cannot change the logging format of the old syslog > daemon. > > reading between the lines I think that you are saying that the server you > are logging to is rsyslog, is this correct? > > If you are logging in rsyslog using a format that includes the timezone, > but the system sending you the log doesn't include what timezone that > server is in, rsyslog makes the guess that the sending server is in the > same timezone as the receiving server and sets the timezone accordingly. > > I would suggest that you compile rsyslog for RHEL5 and replace the syslog > daemon on those systems (the version that came with RHEL5 is old enough > that it's not supported by rsyslog any longer, that version only gets > support from Red Hat) > > The other option would be to put all your systems on the same timezone > (and I would strongly recommend putting them on UTC, it avoids a lot of > hassles) > > David Lang > > > On Fri, 10 Feb 2012, Michael Maymann wrote: > > Hi, >> >> my RHEL5 are legacy syslog clients and they don't report time right. They >> report client-time but server-timezone... >> RHEL6 rsyslog-client did the same thing before i added: >> $ActionForwardDefaultTemplate RSYSLOG_ForwardFormat >> >> >> Br. >> ~maymann >> >> >> 2012/2/10 <[email protected]> >> >> On Fri, 10 Feb 2012, Michael Maymann wrote: >>> >>> Hi List, >>> >>>> >>>> we are running some older RHEL5 syslog-client (that can't be upgraded >>>> due >>>> to software on them) running the old syslog daemon. >>>> I configured my new rsyslog RHEL6 clients with the following: >>>> $ActionForwardDefaultTemplate RSYSLOG_ForwardFormat >>>> and that did the trick for them... >>>> >>>> (How) can I get same result with the old syslog daemon on my syslog >>>> clients >>>> ? >>>> >>>> >>> First off, this sounds like a question to send to RedHat because you are >>> asking how to configure their non-rsyslog daemon. >>> >>> but before we can help you, what is the actual problem you are having? >>> >>> is RHEL5 the sender or the receiver of the log message? >>> >>> what are you getting, and what do you think you should be getting? >>> >>> David Lang >>> ______________________________****_________________ >>> rsyslog mailing list >>> http://lists.adiscon.net/****mailman/listinfo/rsyslog<http://lists.adiscon.net/**mailman/listinfo/rsyslog> >>> <http:**//lists.adiscon.net/mailman/**listinfo/rsyslog<http://lists.adiscon.net/mailman/listinfo/rsyslog> >>> > >>> http://www.rsyslog.com/****professional-services/<http://www.rsyslog.com/**professional-services/> >>> <http://**www.rsyslog.com/professional-**services/<http://www.rsyslog.com/professional-services/> >>> > >>> >>> ______________________________**_________________ >> rsyslog mailing list >> http://lists.adiscon.net/**mailman/listinfo/rsyslog<http://lists.adiscon.net/mailman/listinfo/rsyslog> >> http://www.rsyslog.com/**professional-services/<http://www.rsyslog.com/professional-services/> >> >> ______________________________**_________________ > rsyslog mailing list > http://lists.adiscon.net/**mailman/listinfo/rsyslog<http://lists.adiscon.net/mailman/listinfo/rsyslog> > http://www.rsyslog.com/**professional-services/<http://www.rsyslog.com/professional-services/> > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
