Is there an option that elog creates one logfile for one entry in the
database? It seems that there elog is creating one logfile for one day.

> Is there an option that elog creates one logfile for one entry in the
> database? It seems that there elog is creating one logfile for one day.

No. One file per day was chosen in order to keep the number of files small.
For which purpose would you need such an option?

I want exchange the logs as files and not with the mirroring function. My 
collegue and me are already exchanging all our project files, so the logs from 
ELOG could be included in this exchange.

> I want exchange the logs as files and not with the mirroring function. My 
> collegue and me are already exchanging all our project files, so the logs from 
> ELOG could be included in this exchange.

If you do not want to use the mirroring, then you can extract a single entry with
the "hidden" download command. Like for this entry:

http://midas.psi.ch/elogs/Forum/1039?cmd=Download

Tell your browser to save the result locally and you have a file with just this
message. Note however that if you ship these files around, and combine them with an
existing logbook by copying them to the logbook directory, you could have two
entries with the same ID, in which case elogd would produce unpredictable results.

Hi,

Is there a command line in the configuration files to show all of sub logs 
on the main page of elog instead of clicking on "Expand All" on the top of 
ELOG ?

Thanks

> Hi,
> 
> Is there a command line in the configuration files to show all of sub 
logs 
> on the main page of elog instead of clicking on "Expand All" on the top 
of 
> ELOG ?
> 
> Thanks
Up ! :o)
So I have posted a picture to explain better my question.
So could it be possible to have the index page always expanded ?
thanks for answers.

Alex.

> So I have posted a picture to explain better my question.
> So could it be possible to have the index page always expanded ?
> thanks for answers.

I added a new configuration option "Expand selection page" which defaults to
one. So if nothing is changed in the configuration file, the logbook selection
page is expanded by default. Only if one has very many logbooks and wants back
the old behaviour, one has to add "Expand selection page = 0" in the config
file. The new version is under CVS.

> > So I have posted a picture to explain better my question.
> > So could it be possible to have the index page always expanded ?
> > thanks for answers.
> 
> I added a new configuration option "Expand selection page" which defaults to
> one. So if nothing is changed in the configuration file, the logbook selection
> page is expanded by default. Only if one has very many logbooks and wants back
> the old behaviour, one has to add "Expand selection page = 0" in the config
> file. The new version is under CVS.

Many many Thanks for all Stefan ! :o)

I have defined a new field called "Record Date" to accept the dates from a
previous logging system. I am not too concerned with the timestamp
associated with these old imported entries. But for new entries...
There is no way I am able enter/edit the time into my new field. They all
show as having a time of 12:00. What am I doing wrong? Here is a portion of
my config

-----------------------------------------------------------

Attributes =   Record Date, Spacecraft, Author, SubSystem, Title

Required Attributes = Record Date, Spacecraft, Author, SubSystem, Title

Type Record Date = date
Time format = %A, %d %B, %Y, %H:%M
Date format = %A, %d %B, %Y, %H:%M

Preset Record date = $date
List Display = Record date, Spacecraft, Author, SubSystem, Title
Start page = ?rsort=Record date

Entries per page = 100
Message Height = 15
Page Title = ELOG - $title
Reverse sort = 1
Quick filter = Date, Spacecraft, SubSystem, Author

message comment = "Please make your log entry in the box BELOW."
Attachment Comment = "Please upload your attachment in the box BELOW."

Menu commands = List, New, Edit, Delete, Reply, Find, Help, Download, Last
Day, Move to, Copy to


Subst Author = $long_name from $remote_host
Subst Email = $user_email

RSS Title = $Title, by $author on $Record Date

Guest menu commands = Find, Last 10, Login, Help
Guest Find Menu commands = Find, Last 10, Login, Help

> I have defined a new field called "Record Date" to accept the dates from a
> previous logging system. I am not too concerned with the timestamp
> associated with these old imported entries. But for new entries...
> There is no way I am able enter/edit the time into my new field. They all
> show as having a time of 12:00. What am I doing wrong? Here is a portion of
> my config

Date is "date", and not "date-time" unfortunately. There is no way right now to
enter a time. I plan however to add a new format "datetime", which allows that
option. So stay tuned.

- Stefan

Stefan,

Oh. OK. I will keep tuned. It would be quite useful to have.

Mark
> > I have defined a new field called "Record Date" to accept the dates from a
> > previous logging system. I am not too concerned with the timestamp
> > associated with these old imported entries. But for new entries...
> > There is no way I am able enter/edit the time into my new field. They all
> > show as having a time of 12:00. What am I doing wrong? Here is a portion of
> > my config
> 
> Date is "date", and not "date-time" unfortunately. There is no way right now to
> enter a time. I plan however to add a new format "datetime", which allows that
> option. So stay tuned.
> 
> - Stefan

I implemented a "datetime" option which does exactly what you want. All you
need is a

Type Record Date = datetime

in your config file. The new option is present in version 2.5.8-2 and ready to
download.

When an attached image name contains a space in its filename and attachment
display is enabled elog builds a wrong url to the image:

http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg

instead of the correct one:

http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg

The more annoing thing is that elogs hangs on this. a strace shows a select
on fd n°3 and 5 that loops forever (returning a timeout error):

send(4, "<141>Mar 23 11:36:25 elogd[22189"..., 35, 0) = 35
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)


May be the better solution is, after fixing the bug for backward
compatibility with already uploaded images, to implement a forced characters
substitution at upload time, replacing spaces and every character not in a
"allowed chars" list with an underscore

> When an attached image name contains a space in its filename and attachment
> display is enabled elog builds a wrong url to the image:
> 
> http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg
> 
> instead of the correct one:
> 
> http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg
> 
> The more annoing thing is that elogs hangs on this. a strace shows a select
> on fd n°3 and 5 that loops forever (returning a timeout error):
> 
> send(4, "<141>Mar 23 11:36:25 elogd[22189"..., 35, 0) = 35
> rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
> select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
> select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
> 
> 
> May be the better solution is, after fixing the bug for backward
> compatibility with already uploaded images, to implement a forced characters
> substitution at upload time, replacing spaces and every character not in a
> "allowed chars" list with an underscore

A correction:
the url generated is correct, infact modifing by hand the names of the files and
the "Attachment:" entry in the .log all works fine

the same problem happens if the filename is, for example foo.JPG and not foo.jpg :
http://arcolog.roma2.infn.it:8080/ARCO/050221_171508/Graph3.JPG
loops forever

http://arcolog.roma2.infn.it:8080/ARCO/050221_171508/Graph3.jpg
works correctly


so, elog does not like spaces in filename and/or uppercase extensions. the
solution is, IMHO, to sanify the uploaded filename at uploading time :-)

> When an attached image name contains a space in its filename and attachment
> display is enabled elog builds a wrong url to the image:
> 
> http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg
> 
> instead of the correct one:
> 
> http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg

This is on purpose. If you want to save an attachment locally and right click on
the attachment, and select "Save link as..." in your browser, then the default
file name is taken from the link. If your original file namw was "peeling
002.jpg", then you want again the same name, and not "050309_170709_peeling
002.jpg, because you would have to delete the date/time part of the file name
each time which would be annoying. That's why I have chosen to put an artificial
"/" between the date/time and the original file name. On the elog side, it's
converted correctly back to the file name.

The problem with blanks in attachment names I could not reproduce. See this
post, which contains an attachment with a blank in it. As you can see, this does
not crash the server. 

> > When an attached image name contains a space in its filename and attachment
> > display is enabled elog builds a wrong url to the image:
> > 
> > http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg
> > 
> > instead of the correct one:
> > 
> > http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg
> 
> This is on purpose. If you want to save an attachment locally and right click on
> the attachment, and select "Save link as..." in your browser, then the default
> file name is taken from the link. If your original file namw was "peeling
> 002.jpg", then you want again the same name, and not "050309_170709_peeling
> 002.jpg, because you would have to delete the date/time part of the file name
> each time which would be annoying. That's why I have chosen to put an artificial
> "/" between the date/time and the original file name. On the elog side, it's
> converted correctly back to the file name.
> 

yes I notice this after posting :-) sorry

> The problem with blanks in attachment names I could not reproduce. See this
> post, which contains an attachment with a blank in it. As you can see, this does
> not crash the server. 

Ok I can confirm this.
The problem arises, for me, when upgrading to the new version of elog having yes
some old entries with attached filenames containing spaces and/or uppercase extensions.

It seems that uploading files with spaces in the name *now* works well... so the
problem should be somewhere in the handling of existing attachments, not rised when
the attachment is uploaded with the current version of elog ... it's quite strange

> It seems that uploading files with spaces in the name *now* works well... so the
> problem should be somewhere in the handling of existing attachments, not rised when
> the attachment is uploaded with the current version of elog ... it's quite strange

Can you send me one of this old xxxxxxa.log files which causes that crash, I can then fix
it in elogd.c ...

> When an attached image name contains a space in its filename and attachment
> display is enabled elog builds a wrong url to the image:
> 
> http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg
> 
> instead of the correct one:
> 
> http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg
> 
> The more annoing thing is that elogs hangs on this. a strace shows a select
> on fd n°3 and 5 that loops forever (returning a timeout error):
> 
> send(4, "<141>Mar 23 11:36:25 elogd[22189"..., 35, 0) = 35
> rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
> select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
> select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
> 
> 
> May be the better solution is, after fixing the bug for backward
> compatibility with already uploaded images, to implement a forced characters
> substitution at upload time, replacing spaces and every character not in a
> "allowed chars" list with an underscore

donno if the following is correlated, otherwise there is another problem I
guess :-)
I attached a strace of elog, hope you'll find it useful.

- Irestarted the daemon
- attached strace to it
- requested the list for a testin logbook, few entries some quite big images 
  (two thumbnails, the other are old images get resized my the browser)
- repeted previous point a couple of times
- press F5 (mozilla-firefox)  the browser hangs 4ever
- stop the load
- repeat point 3, all right
- F5 => hangs
- F5 => hangs

there should be some problem, may be in the socket ?

> - Irestarted the daemon
> - attached strace to it
> - requested the list for a testin logbook, few entries some quite big images 
>   (two thumbnails, the other are old images get resized my the browser)
> - repeted previous point a couple of times
> - press F5 (mozilla-firefox)  the browser hangs 4ever
> - stop the load
> - repeat point 3, all right
> - F5 => hangs
> - F5 => hangs

I tried to reproduce this problem, but everything was fine. This problem was never
reported by anyone else as well.

> > - Irestarted the daemon
> > - attached strace to it
> > - requested the list for a testin logbook, few entries some quite big images 
> >   (two thumbnails, the other are old images get resized my the browser)
> > - repeted previous point a couple of times
> > - press F5 (mozilla-firefox)  the browser hangs 4ever
> > - stop the load
> > - repeat point 3, all right
> > - F5 => hangs
> > - F5 => hangs
> 
> I tried to reproduce this problem, but everything was fine. This problem was never
> reported by anyone else as well.

I tried to rise the problem with konqueror, and all works nice... running
mozilla-firefox gives the problem instead (also running the test at the same time), so
there should be something in firefox or in the interaction between firefox and elog.
I'll send you one of the elog giving the problems so you can test by yourself as you
asked.

btw:
http://midas.psi.ch/elogs/Forum/?mode=full&attach=1  does not gives any problem to me
even running firefox. so the problem may be in some my elog.cong parameter ...

> > - Irestarted the daemon
> > - attached strace to it
> > - requested the list for a testin logbook, few entries some quite big images 
> >   (two thumbnails, the other are old images get resized my the browser)
> > - repeted previous point a couple of times
> > - press F5 (mozilla-firefox)  the browser hangs 4ever
> > - stop the load
> > - repeat point 3, all right
> > - F5 => hangs
> > - F5 => hangs
> 
> I tried to reproduce this problem, but everything was fine. This problem was never
> reported by anyone else as well.

running ethereal I found a bug, hope this is the problem hanging my firefox (I think
we have a good chance it is :-P)

when I have thuimbs enabled, elog returns for the ".thumb" (or ".whatever".. thumb's
extension should be transparent to elog .. uhm... it can't be .. this is a problem)

anyway, having attached a pdf (a big one) and aving attachment display enabled (with
my thumbnails generated by my script)  elog returns for the displayed thumb a
Content-Type for application/x-pdf, instead of the correct image/jpeg. I think this is
the problem.

The only way for elog to know what is the correc\t content type for thumbnails is to
get it from a configuration parameter, becouse it is a chioce of the external script
used to generate them to choose the type of thumbs (jpeg, png, gif ... )
One conf parameter defaulting to jpeg may be the solution

Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
as soon as it is accessed.

Under 2.5.7, a login page will come up, and the logbook will work, but only
if a valid username/password is given.  If an invalid login is given, then
elogd crashes.  We have a cron job that periodically restarts elogd if it is
has crashed.

Steve

[global]
logbook tabs = 0
port = 8080
Protect Selection page = 1
Password file = user.info
Admin user = saw
 

> Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> as soon as it is accessed.

Thanks for reporting this bug. I fixed it and committed the change to CVS.

- Stefan

> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
> 
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
> 
> - Stefan

wow, who's Speedy Gonzales ?!? :-P

> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
> 
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
> 
> - Stefan

wow, who's Speedy Gonzales ?!? :-P

> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
> 
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
> 
> - Stefan

That was fast!  I put the elogd.c from the cvs on top of 2.5.8 and now I can run
the server with Protect Selection page=1 again.

Logins work OK if the username/password is valid.  However, if I try to login
with invalid authentication, the server crashes.  If I turn off the protect
selection page, then invalid authentication does not crash elogd.

Thanks, Steve

> Logins work OK if the username/password is valid.  However, if I try to login
> with invalid authentication, the server crashes.  If I turn off the protect
> selection page, then invalid authentication does not crash elogd.

Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))

I fixed that as well and committed the changes.

Greetings to JLab (I once worked at UVa in Charlottesville...). Is David Abbott
still there?

- Stefan

> > Logins work OK if the username/password is valid.  However, if I try to login
> > with invalid authentication, the server crashes.  If I turn off the protect
> > selection page, then invalid authentication does not crash elogd.
> 
> Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> 
> I fixed that as well and committed the changes.

That seems to do the trick!  Thanks, Steve

> > > Logins work OK if the username/password is valid.  However, if I try to login
> > > with invalid authentication, the server crashes.  If I turn off the protect
> > > selection page, then invalid authentication does not crash elogd.
> > 
> > Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> > 
> > I fixed that as well and committed the changes.
> 
> That seems to do the trick!  Thanks, Steve

Hi,
where can I find this correction for ELOG?
thanks a lot :o)

> > > > Logins work OK if the username/password is valid.  However, if I try to login
> > > > with invalid authentication, the server crashes.  If I turn off the protect
> > > > selection page, then invalid authentication does not crash elogd.
> > > 
> > > Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> > > 
> > > I fixed that as well and committed the changes.
> > 
> > That seems to do the trick!  Thanks, Steve
> 
> Hi,
> where can I find this correction for ELOG?
> thanks a lot :o)

It's under CVS. You have to recompile the executable yourself, or you wait for the next
release (;-)

I would like to create a paper waste logbook. I need to have a column that 
shows a weight in pounds and another column with a calculation from those 
pounds to dollars.  pounds x $4.00 = cost  I was wondering if this was 
possible? 

All other fields would be just Date, Batch#, Operator, Reason, Process 
Operator, Manager, Lbs, and Cost,  I would also like to total this cost if 
possible, on a search selected basis. Similar to Excel.

Thanks for any input

David Egolf

> I would like to create a paper waste logbook. I need to have a column that 
> shows a weight in pounds and another column with a calculation from those 
> pounds to dollars.  pounds x $4.00 = cost  I was wondering if this was 
> possible? 
> 
> All other fields would be just Date, Batch#, Operator, Reason, Process 
> Operator, Manager, Lbs, and Cost,  I would also like to total this cost if 
> possible, on a search selected basis. Similar to Excel.

Unfortunately not. But your request is on the wishlist since some time, I added
your vote.

> as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp


> it should be used an HTML entity instead of the ampersand sign.<p>

Can you please be a bit more specific? In which URL should the ampersand be
replaced?

> > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> 

> > it should be used an HTML entity instead of the ampersand sign.<p>
> 
> Can you please be a bit more specific? In which URL should the ampersand be
> replaced?

uhmm...

http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7

the bug is also a "documentation bug", infact similar tricks are also
in FAQs (FAQ 5 for example)

I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does
not do the job at all ... infact the first time the HTML code is ok, but
following a link let the browser to automatically decode html entities .. and
everything turns wrong again ... maybe the encoding should be done in
printing-to-the-browser-time ..

> > > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> > 

> > > it should be used an HTML entity instead of the ampersand sign.<p>
> > 
> > Can you please be a bit more specific? In which URL should the ampersand be
> > replaced?
> 
> uhmm...
> 
> http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7
> 
> the bug is also a "documentation bug", infact similar tricks are also
> in FAQs (FAQ 5 for example)
> 
> I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does
> not do the job at all ... infact the first time the HTML code is ok, but
> following a link let the browser to automatically decode html entities .. and
> everything turns wrong again ... maybe the encoding should be done in
> printing-to-the-browser-time ..

BTW, the current url (taht should be perfectly well formed makes the elog not to
display attachments ... so may be thare is a problema in the query string decoding
routine ...

http://somehost.it:8080/LBNAME/?mode=full&amp;attach=1

> > > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> > 

> > > it should be used an HTML entity instead of the ampersand sign.<p>
> > 
> > Can you please be a bit more specific? In which URL should the ampersand be
> > replaced?
> 
> uhmm...
> 
> http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7
> 
> the bug is also a "documentation bug", infact similar tricks are also
> in FAQs (FAQ 5 for example)
> 
> I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does
> not do the job at all ... infact the first time the HTML code is ok, but
> following a link let the browser to automatically decode html entities .. and
> everything turns wrong again ... maybe the encoding should be done in
> printing-to-the-browser-time ..

BTW, the current url (taht should be perfectly well formed makes the elog not to
display attachments ... so may be thare is a problema in the query string decoding
routine ...

http://somehost.it:8080/LBNAME/?mode=full&amp;attach=1

> > I tried to substitute avery occurrence of hard coded "&" with "&" but it does
> > not do the job at all ... infact the first time the HTML code is ok, but
> > following a link let the browser to automatically decode html entities .. and
> > everything turns wrong again ... maybe the encoding should be done in
> > printing-to-the-browser-time ..

That won't help, since the 'Start page = ...' string is used for redirection (outside
of any HTML). The '&' thing should only occur inside the HMTL text.

I changed elogd.c to encode things properly, but I'm not sure if I covered all
occurences. Can you try release 1.576 if it works correctly?

> as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp


> it should be used an HTML entity instead of the ampersand sign.<p>

another problem with validation:
required attribute "ALT" not specified  in every <img> tag used in the elog (icons)

here is an example of the validator results:
http://validator.w3.org/check?uri=http%3A%2F%2Fmidas.psi.ch%2Felogs%2FLinux+Demo%2F&charset=iso-8859-1+%28Western+Europe%29&verbose=1

I added ths missing tags. The validator at least does not complain any more.

Stefan, the validation still fails on the ampersand ... here is an example of your online Demo elog: http://validator.w3.org/check?verbose=1&uri=http%3A//midas.psi.ch/elogs/Forum/920

> Stefan, the validation still fails on the ampersand ...
> here is an example of your online Demo elog:
> http://validator.w3.org/check?verbose=1&uri=http%3A//midas.psi.ch/elogs/Forum/920

Ok, I fixed that, the validation link above show a valid page.

Hi to all,

I've prepared a new Debian package.  This version will probably be the one
which you'll find in Sarge/stable.

There are some invasive changes in this version which call for a serious
test.  In accordance with a suggestion, I've changed the configuration
mechanism.  For details, please read the NEWS.Debian file attached.

Could the Debian users who follow this forum test it and give some feedback?
You can download the package from the following link:

  http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb

Thanks in advance for your participation,

> Hi to all,
> 
> I've prepared a new Debian package.  This version will probably be the one
> which you'll find in Sarge/stable.
> 
> There are some invasive changes in this version which call for a serious
> test.  In accordance with a suggestion, I've changed the configuration
> mechanism.  For details, please read the NEWS.Debian file attached.
> 
> Could the Debian users who follow this forum test it and give some feedback?
> You can download the package from the following link:
> 
>   http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
> 
> Thanks in advance for your participation,

It seems to work nice to me.
Just another suggestion: I think it would be better to insert a commented out
example for all allowed parameters in the distributed  /etc/default/elog

nice work :-)

> It seems to work nice to me.
> Just another suggestion: I think it would be better to insert a commented out
> example for all allowed parameters in the distributed  /etc/default/elog

Thanks for the test.  Please note that, /etc/default/elog is partially auto
created during the installation.  All options except PIDFILE and CONFFILE are
currently listed (as configured or commented out).  If you didn't see these
options (after the update), there must be a problem.   Did you mean the lack of
PIDFILE and CONFFILE in the default file?

> > It seems to work nice to me.
> > Just another suggestion: I think it would be better to insert a commented out
> > example for all allowed parameters in the distributed  /etc/default/elog
> 
> Thanks for the test.  Please note that, /etc/default/elog is partially auto
> created during the installation.  All options except PIDFILE and CONFFILE are
> currently listed (as configured or commented out).  If you didn't see these
> options (after the update), there must be a problem.   Did you mean the lack of
> PIDFILE and CONFFILE in the default file?

no, my bad (it seems :-P) .. I re-installed the package now on my laptop and seems
to work fine... maybe I have swapped the diff result when installed yesterday.

Making tests I found another problem, her is the report:

####
root@emc2:/home/albert# apt-get remove elog
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti saranno RIMOSSI:
  elog
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
È necessario prendere 0B di archivi.
Dopo l'estrazione, verranno liberati 2444kB di spazio su disco.
Continuare? [S/n]
(Lettura del database ... 152033 file e directory attualmente installati.)
Rimuovo elog ...
Stopping ELOG daemon: elogd.
root@emc2:/home/albert# rm /etc/default/elog
rm: rimuovere regular file `/etc/default/elog'? y
root@emc2:/home/albert# apt-get install elog
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti NUOVI (NEW) saranno installati:
  elog
0 aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prendere 0B/530kB di archivi.
Dopo l'estrazione, verranno occupati 2444kB di spazio su disco.
Selezionato il pacchetto elog, che non lo era.
(Lettura del database ... 151926 file e directory attualmente installati.)
Spacchetto elog (da .../elog_2.5.8+r1592-1_i386.deb) ...
Configuro elog (2.5.8+r1592-1) ...
cat: /etc/default/elog: No such file or directory
Starting ELOG daemon: elogd.
####


So, removing an existing elog (not purging) and installing again raise the error.
Why installation creates the default/elog file only the first time ?  I think it
shoud do the job everytime (and everytime ask the user is there is a diff to be
checked)

> Hi to all,
> 
> I've prepared a new Debian package.  This version will probably be the one
> which you'll find in Sarge/stable.
> 
> There are some invasive changes in this version which call for a serious
> test.  In accordance with a suggestion, I've changed the configuration
> mechanism.  For details, please read the NEWS.Debian file attached.
> 
> Could the Debian users who follow this forum test it and give some feedback?
> You can download the package from the following link:
> 
>   http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
> 
> Thanks in advance for your participation,

btw, what about in including in default/elog also a voice for the "-x" switch ??

It is a security related thing and may be passed only on the command line to the
daemon, so it should be governed by the system elog admin.