Multi Language based on logged on user?, posted by Hal Proctor on Thu May 16 15:41:34 2013
|
Can ELog support different languages based on the logged on user? |
|
Moving password file, posted by UlfO on Fri Aug 16 11:54:17 2013
|
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
|
Moving individual messages in a thread, posted by Eoin Butler on Sat Sep 13 23:34:37 2008
|
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? |
|
Moving entry (and replies) from one log book to another, posted by David Pilgram on Fri May 1 14:01:44 2009
|
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. |
|
Moving eLog from Server to Server..., posted by Charles Duncan on Sat Jun 11 02:29:01 2005
|
I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file??
-Charles- |
|
Moving a logbook from one installation to another, posted by Val Schmidt on Mon Dec 17 02:17:20 2007
|
I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
What I find is
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates.
c) The numbering of entries has been reset to 1.
Can anyone explain what I've done to mucky this up and how to fix it?
Thanks in advance,
Val
|
Move to: elog crashes with large no of entries being moved., posted by David Pilgram on Wed Jun 10 13:56:09 2009
|
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. |
|
More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
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 |