diff --git a/doc/config.html b/doc/config.html index 2651e933..9499583c 100755 --- a/doc/config.html +++ b/doc/config.html @@ -339,12 +339,25 @@ if several logbooks use the same images and icons, but differnt colors. By defau the CSS default.css is used. This can be overwritten by this statement.

+

  • Title image = <string> +
    +HTML code for the icon in the upper right corner. By default, following code +is used:

    + +<img border=0 src="elog.gif" alt="ELOG logo">

    + +This code can be replaced by <string> to display a different +icon file, or to display some text. The icon image has to be present in the theme directory, +which is usually <elog root>/themes/default. +

    +

  • Title image URL = <URL>
    The ELOG icon at the right upper corner usually points to the ELOG home page. This URL can be changed to point to a corporate page for example with this option. The icon can be changed by replacing the elog.gif icon in the -theme directory. +theme directory. This option should only be used if the Title image +option is not used.

  • Date format = <string> @@ -855,6 +868,28 @@ Values used for new message entry form: Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be ommitted, so specifying for example only the flags is possible. +

    + +

  • Execute new | edit | delete = <command> +
    +It is possible to execute a shell command on the server side after a new message +has been submitted, edited or deleted. This feature has been used in the past +for SMS notifications over a telephone system and for synchrnonization of the ELOG +database with an external SQL database. The <command> can +contain substitutions similar to the Subst command. +Following (Unix) command writes a notification into some file:

    + +

    +Execute new = echo "New message of type $type from $long_name on $remote_host" >> /tmp/elog.log
    +
    +
    +It should be noted that this feature can impose a security problem. If someone can edit +the elogd.cfg through the Config command of elogd, that person +can put malicious code into elogd.cfg and execute it. This is even more severe if elogd +runs with root privileges. To avoid such problems, the execute facility is disabled +in elogd by default and has to be enabled explicitly with the "-x" command line flag. +The administrator has to ensure then of course that only trusted people can edit elogd.cfg. +