Re: Max Logbooks for Email notify, posted by Stefan Ritt on Wed Apr 22 13:40:19 2015
|
Ok, I fixed this in the current GIT version. You might check if that works for you.
| Oliver Kleinau wrote: |
|
It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!!
| Oliver Kleinau wrote: |
|
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
| Oliver Kleinau wrote: |
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|
|
|
Remote entries with empty messages possible?, posted by Edmund Hertle on Fri May 8 17:45:24 2015
|
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111
But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:
elog -h elog-server-adress -l EO -a Fill=111 "test"
also using an empty string does not work:
elog -h elog-server-adress -l EO -a Fill=111 ""
I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.
To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done. |
|
Re: Remote entries with empty messages possible?, posted by Stefan Ritt on Mon May 11 13:15:54 2015
|
The "command does not respond" means that the program starts reading in the main message text from the console. You can type several lines of text, and finish it off by hitting Ctrl-D (Ctrl-Z under Windows).
I see your point of having empty texts. Indeed the "" on the command line does not work presently, so you have to add a space as a workaround. I modified the elog code (committeed to bitbucket repository) to accept "" as empty text to suit your needs.
/Stefan
| Edmund Hertle wrote: |
|
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111
But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:
elog -h elog-server-adress -l EO -a Fill=111 "test"
also using an empty string does not work:
elog -h elog-server-adress -l EO -a Fill=111 ""
I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.
To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.
|
|
|
Re: Remote entries with empty messages possible?, posted by Andreas Luedeke on Mon May 11 22:51:44 2015
|
Hi Edmund,
Stefan already supplied a fix, but you could as well use a workaround: provide an empty file as text. The following works for Linux:
elog -h elog-server-adress -l EO -a Fill=111 -m /dev/null
Cheers
Andreas
| Edmund Hertle wrote: |
|
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111
But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:
elog -h elog-server-adress -l EO -a Fill=111 "test"
also using an empty string does not work:
elog -h elog-server-adress -l EO -a Fill=111 ""
I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.
To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.
|
|
|
csv import timestamp, posted by Ferdinand Gassauer on Wed May 13 22:03:37 2015
|
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
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
| Ferdinand Gassauer wrote: |
|
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
|
Re: csv import timestamp, posted by Ferdinand Gassauer on Thu May 14 07:01:23 2015
|
Thanks
what is the format of the Date field in the csv file ?
My Date is date and not datetime.
| Andreas Luedeke wrote: |
|
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
| Ferdinand Gassauer wrote: |
|
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
|
|
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
| Ferdinand Gassauer wrote: |
|
Thanks
what is the format of the Date field in the csv file ?
My Date is date and not datetime.
| Andreas Luedeke wrote: |
|
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
| Ferdinand Gassauer wrote: |
|
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
|
|