Re: Attribute not updated, posted by Andreas Luedeke on Thu May 14 02:02:45 2015
|
Hi Francois,
as far as I know there is a limit on the number of conditions you can use (See elog:67303).
I guess you did hit that limit.
|
Re: csv import timestamp, posted by Andreas Luedeke on Thu May 14 02:19:53 2015
|
Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry
time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm.
Did you have any problems doing it?
Cheers
Andreas
|
Re: Attribute not updated, posted by Andreas Luedeke on Thu May 14 04:59:03 2015
|
> Seriously, I really hope It could make it... Could you try it on your side ?
|
Re: Elogd synchronisation with remote server, posted by Andreas Luedeke on Thu May 14 05:13:34 2015
|
> I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
> elogd mention "-m" and "-M" ... not elog but elogd... with that description :
> synchronize logbook(s) with remote server
|
Re: csv import timestamp, posted by Andreas Luedeke on Thu May 14 22:16:03 2015
|
Hi Ferdinand,
"import" is meant to be used for files that have been exported with "find". Therefore it is not very
flexible with the date format.
Todays date should look like that: "Thu 14 May 2015 22:12:00 +0200".
You have
to convert your file that the date matches this format (BTW: I found this out by using the find - export feature; it may depend on a local configuration.)
Cheers
Andreas
|
Re: Entry size too large for email notification, posted by Andreas Luedeke on Tue May 19 16:34:20 2015
|
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile
after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But
I think that an 2.2 MB image should easily fit into that.
Andreas
|
Re: elogd moves elog entries, posted by Andreas Luedeke on Wed May 20 11:59:59 2015
|
> elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
> in the release announcement and in the release and migration notes. K.O.
|
Re: elogd moves elog entries, posted by Andreas Luedeke on Wed May 20 18:46:27 2015
|
> Stefan told me that the change was because some users were having thousands of yymmdda.log files
> in the logbook directories, and that sorting them into subdirectories by year at least did something to bring some
> order. Possibly to get around the lazy archivers, I suspect.
|