Re: Modification aren't accepted, posted by Stefan Ritt on Thu Jan 20 08:51:13 2011
|
David Pilgram wrote:
|
|
Re: Modification aren't accepted, posted by bob on Thu Jan 20 13:49:22 2011
|
Stefan Ritt wrote:
|
|
Re: Modification aren't accepted, posted by Stefan Ritt on Thu Jan 20 13:52:04 2011
|
bob wrote:
|
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Fri Jul 31 15:42:55 2020
|
Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you
might have a wrong path in elogd.cfg
VUIIS |
|
Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Fri Jul 31 21:40:02 2020
|
On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.
On the old server after stopping elogd i get:
/usr/sbin/elogd -v 3 |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sat Aug 1 15:13:17 2020
|
You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files
in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.
Stefan |
|
Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Sun Aug 2 02:57:59 2020
|
Thank-you. That is good information to have.
What is the default if you you do not specify anything in elogd.cfg? I assume it is /usr/local/elog otherwise it would not see the existing
logbooks. |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sun Aug 2 09:06:46 2020
|
If nothing is specified elogd looks for logbooks in the current directory where it got started under ./logbooks/
No idea what happened to your 2020 logbook.
VUIIS |