I'm not exactly sure what you want to do, but there are two options in elog:

1) Insert directly a table like this one:

2) Use one ELOG entry as a row in a table. You can try this by clicking on "List" here in the Forum should you not already see the list display, then on "Summary" which give you a spreadsheet like display, where you can specify in the config file which columns of the ELOG entries you want to see. See also the demo here: https://elog.psi.ch/elogs/Linux+Demo/

Best,

Stefan

A statement like "core dumped" does not help much. Same with valgrind memory leaks. I need a full strack trace with all parameters when the segment violation occurs. The easiest is when you run elogd vom inside gdb, and once you get the signal, do a "where" to see th full stack trace.

As you can see from this forum, there is absolutely no crash when you upload any file, so it must have to do with your config file or anything whcih is special in yoru environment. We have to find what this is so that I can reproduce it here.

Stefan

Hello,

I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.

For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:

http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date

Can you please help me?

Here I reduced my elogd.cfg at minimum and I still get this issue:

[global]
port = 8080

[65 nm]
Attributes = Record date

Type Record date = datetime
Preset Record date = $date
List Display = Record date
Start page = ?sort=Record date

Dear Stefan,

thanks to the answer you gave to my colleague. 

Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,

1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks? 

2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?

thanks

Matteo

I just read all administrator guide especially in :

http://midas.psi.ch/elog/config.html#access

and I didnt find it that exactly match with my need, or maybe I read wrong section :P

maybe my explanation little bit general.

I'll try to explain in detail, In my office, I just create 1 logbook for all employee,

one of my friend ask me if it possible to only give few people the ability to read all entry inside the logbook (all members), and the others (rest of the members) only able to input entry in the logbook and read their own.

please guide us.