Hi,

Is it possible to move a passwordfile from one E-log to another E-Log located on a different server without the need for users to register again?

Regards
/UlfO

It is possible that the Move to... and Copy to... commands can be configured so that when they operate on a message that is part of a thread, that only that message will be moved, instead of the whole thread?

Hi Stefan,

When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
the entries' ID number(s) ($@MID@$).  While it may not be good practice, we've referred to these numbers in
cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
your FAQ about marking of whole threads).

In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
ID number.

Thanks,

David Pilgram.

Hi Stefan,

I've been slowly moving threads, and twice now so far (and reproducably) had elog crash.

In each case, it is trying to move a thread with more than 24 entries; it copies the first 24 entries, then
crashes with "Segmentation Fault".  It does not erase the lock file /var/run/elog.pid

I have got around this by manually copying the entries beyond no 24, then deleting the thread entry by entry.

I am aware that I have an old and limited machine (586, 256MB RAM, running Slack 10), and at first I was
"content" to write it off as that; but when it crashed for the second time at exactly the same entry (the
twenty-forth) even though the size of the entries would have been significantly different, I wondered if there
was some factor within  elog that could affect this.

I've not tried it with Copy to:, but imagine it will also be affected as the only difference with this and Move
to: is the deletion of the thread after all the entries had been copied.

I am modifying the elogd.cfg automatically with a script.  The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.

Everything worked fine, until we hit the critical number of 100 attributes.  I saw this is also stated in the manual.

Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior. 

Is there a reason for this limit?

Thanks

Jonathan

I am running 2.5.8-3 with the elogd.c 1.632.  I have attached the config
file that I am using.   I have a top group "src", with logbooks "SRC
Analysis" and "SRC Mail" in it.  These two logbooks share the same password
file.  If one logs into one, I would like them to be not have to login to
the other.  If I put the password file name under [global src], I get this
behaviour, but the logbook selection page does not show my graphic or the
locks by the logbook names (instead it has the Alt text "This logbook
requires authentication."  If I remove the password from [global src] and
put it in each logbook individually, then my logbook selection page looks
OK, but I have to log into each logbook seperately.

Stephen