Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 272 of 807  Not logged in

Find |  Login |  Help

Full | Summary | Threaded | Collapse | Expand     -- All entries -- Last day Last 3 Days Last week Last month Last 3 Months Last 6 Months Last Year -- Category -- Info Bug report Bug fix Question Request Comment Other  6451 Entries

Goto page Previous  1, 2, 3 ... 271, 272, 273 ... 805, 806, 807   Next

Date attribute in Quick filter, posted by Peter Rienstra on Thu Oct 25 12:04:02 2007  Stefan, I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:       Re: Date attribute in Quick filter, posted by Stefan Ritt on Thu Oct 25 20:15:46 2007  [quote="Peter Rienstra"]I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get: Error: "Attribute "Date" for quick filter not found", see attachment.   elogd dies after receiving second SIGHUP, posted by Kester Habermann on Tue Nov 11 16:45:04 2008  elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates. This was observed on Solaris 10 (SPARC). The documentation states that elogd should re-read configuration after receiving SIGHUP.       Re: elogd dies after receiving second SIGHUP, posted by Stefan Ritt on Mon Nov 17 10:27:23 2008  > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates. > This was observed on Solaris 10 (SPARC). > The documentation states that elogd should re-read configuration after receiving SIGHUP.       Re: Change background color, posted by Stefan Ritt on Mon Dec 8 08:59:56 2008                              mike cianci wrote:                                      Re: elogd dies after receiving second SIGHUP, posted by Paul T. Keener on Wed Jun 3 19:53:13 2009  > > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates. > > This was observed on Solaris 10 (SPARC). > > The documentation states that elogd should re-read configuration after receiving SIGHUP.       Re: elogd dies after receiving second SIGHUP, posted by Stefan Ritt on Thu Jun 4 09:49:13 2009  > > > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates. > > > This was observed on Solaris 10 (SPARC). > > > The documentation states that elogd should re-read configuration after receiving SIGHUP.       Re: elogd dies after receiving second SIGHUP, posted by Paul T. Keener on Thu Jun 4 18:49:29 2009  > > > > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates. > > > > This was observed on Solaris 10 (SPARC). > > > > The documentation states that elogd should re-read configuration after receiving SIGHUP.

Goto page Previous  1, 2, 3 ... 271, 272, 273 ... 805, 806, 807   Next

ELOG V3.1.5-3fb85fa6