my_shell (OS_UNIX) uses /tmp/elog_shell - conflict when more than one elogd runs at the same time, posted by John M O'Donnell on Fri May 20 22:45:00 2011 
|
all instances of elogd use the same file name in /tmp when calling my_shell. This can cause some inconsistent behavior when two or more copies
of elogd are runnnig at the same time. (eg. one might detect ImageMagik is installed, and the other not,)
|
|
Re: Elog crashes with URL find npp=0, posted by Andreas Luedeke on Tue Sep 13 13:38:19 2011
|
> [...] It appears that npp=0 crashes elogd [...]
Here's a patch: search for "npp" in src/elogd.c and add the following line:
|
Re: ssl problems, posted by Andreas Luedeke on Sat Feb 11 05:43:33 2012
|
John Doroshenko wrote:
|
|
Re: ssl problems, posted by Christian Herzog on Sat Feb 11 22:05:36 2012
|
Andreas Luedeke wrote:
|
|
Re: ssl problems, posted by Andreas Luedeke on Sat Feb 11 22:19:07 2012
|
Christian Herzog wrote:
|
|
Re: ssl problems, posted by Christian Herzog on Sat Feb 11 22:27:15 2012
|
| well it's not a server but my laptop, but yeah, the elog server and the browser ran on the same machine, no iptables. |
|
Re: ssl problems, posted by Andreas Luedeke on Sat Feb 11 22:37:34 2012
|
> well it's not a server but my laptop, but yeah, the elog server and the browser ran on the same machine, no iptables.
Strange: I thought I was able to reproduce your problem, but no: whatever browser I try I can access ELOG with SSL if
|
|
Re: ssl problems, posted by Olaf Kasten on Mon Feb 13 21:44:05 2012
|
> > well it's not a server but my laptop, but yeah, the elog server and the browser ran on the same machine, no iptables.
>
> Strange: I thought I was able to reproduce your problem, but no: whatever browser I try I can access ELOG with SSL if
|