Hi John,

Thanks for the message! I’ve downloaded CKEditor version 4.22, since newer versions are no longer fully open source and come with restrictive licensing.  I now have the full CKEditor 4.22 package locally, but I’m not quite sure what the next step is. Should I place it somewhere specific in the ELOG directory structure or modify one of the templates to enable it? Any pointers on how to connect it properly to ELOG would be very helpful.

Best regards,
Pawel

Hi John,

Thanks for the message! I’ve downloaded CKEditor version 4.22, since newer versions are no longer fully open source and come with restrictive licensing.  I now have the full CKEditor 4.22 package locally, but I’m not quite sure what the next step is. Should I place it somewhere specific in the ELOG directory structure or modify one of the templates to enable it? Any pointers on how to connect it properly to ELOG would be very helpful.

Dear All,

is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find the corresponding option in the available docs/ sample config files...

-- many thanks, regards, Pasha

Hi noob question I was looking for a config but i cant make it, how to i make multitab logbook like this page?

Like in Discussion there are forum,config examples,contribution and vulnerabilities under it

Thanks

 NVM found it Thanks

> > 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.
> 
> I tried to reproduce this but without success. I could send many SIGHUPs without the daemon terminating. Maybe 
> you modified the configuration file in between and elogd barked out because of some wrong configuration? Try to 
> start the daemon interactively and see what exactly happens if you send several SIGHUPs.

The problem is that under Solaris signal handlers installed via signal() get uninstalled *before* the signal handler
is called.  Thus the second time elogd receives a SIGHUP, you get the default action, which is to kill the process.

The solution is to use the POSIX sigaction() call instead of signal(). 

> > > > 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.
> > > 
> > > I tried to reproduce this but without success. I could send many SIGHUPs without the daemon terminating. Maybe 
> > > you modified the configuration file in between and elogd barked out because of some wrong configuration? Try to 
> > > start the daemon interactively and see what exactly happens if you send several SIGHUPs.
> > 
> > The problem is that under Solaris signal handlers installed via signal() get uninstalled *before* the signal handler
> > is called.  Thus the second time elogd receives a SIGHUP, you get the default action, which is to kill the process.
> > 
> > The solution is to use the POSIX sigaction() call instead of signal(). 
> 
> Can you try to modify the signal() calls into sigaction(). If this really works under Solaris, I will incorporate this 
> then into the distribution.

Here is the patch.  It works under both Solaris and Linux.