Hmm. Not sure that is accurate. This is an example where I log to local syslog: == <174>0 2017-03-14T19:04:31.891156+00:00 ulogd log_flowlog_log [DESTROY] ORIG: SRC=10.0.202.196 DST=10.0.202.201 PROTO=TCP SPT=52094 DPT=5001 PKTS=12060 BYTES=699112736 , REPLY: SRC=10.0.202.201 DST=10.0.202.196 PROTO=TCP SPT=5001 DPT=52094 PKTS=8972 BYTES=466636 On Tue, Mar 14, 2017 at 12:47 PM, Sven-Haegar Koch <haegar@xxxxxxxxx> wrote: > On Tue, 14 Mar 2017, Muhammad Faisal wrote: > >> I would like to understand is this a feature or a possible bug that >> Year info is missing from the ulogd2 output. >> >> >> Mar 11 15:55:59 wc01 ulogd[14289]: [NEW] ORIG: SRC=5.55.22.172 >> DST=192.168.1.3 PROTO=TCP SPT=2083 DPT=5158 PKTS=0 BYTES=0 , REPLY: >> SRC=192.168.1.3 DST=5.55.22.172 PROTO=TCP SPT=5158 DPT=2083 PKTS=0 >> BYTES=0 > > That is because historically the syslog output format does not contain > the year. Perhaps in the dark unix ages noone thought that you could > keep logs longer... > > c'ya > sven-haegar > > -- > Three may keep a secret, if two of them are dead. > - Ben F. > -- > To unsubscribe from this list: send the line "unsubscribe netfilter" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
