Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 404 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  67553   Fri Aug 16 12:01:56 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2Re: Moving password file

UlfO wrote:

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

Yes. Just make sure that both elog servers are not running when you move the password file. 

  65981   Thu Sep 18 14:39:17 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Moving individual messages in a thread

 

Eoin Butler wrote:

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?

 

 This has not been implemented on purpose. Assume you have a thread with

A

    B

       C

So A links to B, B links back to A and so on. If you would move now B into another logbook, A and C would point to an entry which does not exist any more. Furthermore, C may contain some sentences which are a reply to something which has been said in B. So even if the "Move To" mechanism would re-link A to C and C to A, the entry C would maybe make no sense any more if B is missing. That's why you only can move threads as a whole. If you want to move individual messages, don't use replies. You can actually disable the reply command in the configuration file.

  66373   Thu Jun 4 15:21:23 2009 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.6-2191Re: Moving entry (and replies) from one log book to another
Hi Stefan,

Any possibility on this one?

David Pilgram.
> 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.
  66379   Fri Jun 5 11:29:43 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.6-2191Re: Moving entry (and replies) from one log book to another
> 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.

I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the 
configuration. I have not tested this extensively, but I'm sure you will do it ;-)
  66380   Fri Jun 5 12:02:45 2009 Agree David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.6-2191Re: Moving entry (and replies) from one log book to another
Thanks Stefan,  Downloading shortly and I'll let you know ;-)
> > 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.
> 
> I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the 
> configuration. I have not tested this extensively, but I'm sure you will do it ;-)
  1191   Mon Jun 13 17:45:47 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Moving eLog from Server to Server...

Charles Duncan wrote:
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??


Of course you have to start elogd after you copied all files over, but I presume you did that. The password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook (via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you checked the file permission of the password file? Maybe the user name elogd is running under has no read access to it.
  1192   Mon Jun 13 18:45:45 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
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??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.
  1193   Wed Jun 15 00:20:56 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Charles Duncan wrote:

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
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??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.


I wanted to add that the elog.pwd file did transfer when I used the "elogd -C <url>" command, but the passwords and accounts were not recognized. Also I edited my elog.conf file to contain the absolute address of my elog.pwd file.
ELOG V3.1.5-3fb85fa6