> There is a read password ("Read Password=..." entry in elogd.cfg) on
> the logbook which I cannot bypass from the client.

This is correct. The elog utility works with write passwords and user level access
(specifying a password file), but not with read passwords, that's not implemented. Use a
password file and you should be fine.

> There is a required attribute called "Publiek", and it's defined as
> MOptions. Whenever I try to upload, I keep getting the message that 
> it misses this attribute.

Your problem is that you try to combine a MOptions with a "-r <n>" (reply-to) option. I
have never tried that and found there is a problem. I changed the way MOptions are
submitted. Instead of using <name>_0, <name>_1 etc, you can now do a 

-a "<attrib>=<value1> | <value2>"

This also solves the problem with the "-r" option. You have to upgrade elogd.c from CVS.

This solved the problems, thanks for the fast response!

On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
Reply" is set, the attributes in this list shouldn't be supplied with the command line client.

Anyway, my problem is solved. Thanks for the great product.

Pieter.

> On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
> Reply" is set, the attributes in this list shouldn't be supplied with the command line client.

Well, don't shoot yourself in the foot! The communication between elog and elogd is limited. elog
more or less submits "blindly" whatever you give it on the command line. If "Fixed Attributes
Edit/Reply" is set in the configuration, this only affects the web page with the entry form, so
these attributes are not shown as edit boxes. They are not checked during submission by elogd. Now
to get the same functionality with elog, elog whould have to retrieve the full entry form, analyze
the HTML code, find out which attributes have edit boxes and which ones not. So that's a lot of
work. Since most people use elog in scripts, they set it up once and forever correctly. There are
actually a few people which even want the functionality that elog can change attributes which are
normally fixed.

- Stefan

Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client?

> Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client?

I did modify it already, see http://midas.psi.ch/elog/userguide.html at the bottom.

Hello,
I have been running Elog for a long time on a variety of RedHat releases,
(this is a terrific project by the way). Currently running Elog v2.5.7 on 
RedHat (Fedora Core-II) and most is working great excepting being able to 
modify the default fonts being used by Elog when trying to write and save 
in text mode while in Elog's main editing screen. 

On my setup the font size is way too small and to work around this problem 
I write and save everything in HTML mode. I've browsed the Elog css file 
but don't yet see where or how to properly set the default font style or 
size for the main screen in the editor. Can you shed some light on this for 
me?

--
Regards, Greg

> Hello,
> I have been running Elog for a long time on a variety of RedHat releases,
> (this is a terrific project by the way). Currently running Elog v2.5.7 on 
> RedHat (Fedora Core-II) and most is working great excepting being able to 
> modify the default fonts being used by Elog when trying to write and save 
> in text mode while in Elog's main editing screen. 
> 
> On my setup the font size is way too small and to work around this problem 
> I write and save everything in HTML mode. I've browsed the Elog css file 
> but don't yet see where or how to properly set the default font style or 
> size for the main screen in the editor. Can you shed some light on this for 
> me?

The text style of the main message text is defined in the following lines in the
CSS field:

.messagepre {
  font-family:'lucida console',courier,monospace;
  font-size:10pt;
}

Locate these lines and change 10pt to 12pt or even 14pt.

well, here's the problem that i had: my charset (koi8-u) was specified in elog.conf for every logbook, but this had no effect, and all elog pages continued tu appeared as iso-8859-1 (which is the default)

when i specified charset in the global section, the problem's gone away.

2do: i think it's worth testing how does it work whet charset specified for a separate logbook overrides globally specidied charset

elog version that is in use: 2.5.7 from debian sarge 3.1 r0a powerpc