Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 759 of 807  Not logged in ELOG logo
    icon2.gif   Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Andreas Luedeke on Mon Feb 8 15:07:05 2016 
You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.

Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended
- allows write access for "others")
    icon2.gif   Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Andreas Luedeke on Mon Feb 8 16:27:45 2016 
The process elogd runs as the user "nobody". This user obviously cannot write to /usr/local/elog/logbooks/demo.

But apparently you've created the wrong directory anyway: you've listed /usr/local/elog/demo, but ELOG looks for /usr/local/elog/logbooks/demo.

Cheers, Andreas
    icon2.gif   Re: Find empty attributes, posted by Andreas Luedeke on Wed Feb 17 18:08:53 2016 
It is possible for normal string attributes: the regular expression pattern "^$" can be used to search for an empty string.

E.g.
in this Forum "ELOG Version" is a required attribute, and should never be empty. But if you search for:

https://midas.psi.ch/elogs/Forum/?mode=threaded&reverse=0&reverse=1&npp=8&ELOG+Version=^%24

you'll
find a couple of entries from a time where it apparently wasn't a required attribute.

Cheers

Andreas

    icon2.gif   Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Sun Feb 28 18:24:58 2016 
[quote="Juergen Diefenbach"]I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the
    icon2.gif   Re: Attribute Field Size Limited to 255 Characters, posted by Andreas Luedeke on Thu Mar 3 14:51:55 2016 
No. At least there is no simple method.

You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have
a hard time finding the right one to increase.
    icon2.gif   Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Tue Mar 8 14:12:26 2016 
[quote="Juergen Diefenbach"][quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour
changes:
Save drafts = 0
    icon2.gif   Re: upgrade problem, posted by Andreas Luedeke on Wed Mar 16 08:39:55 2016 
Hi Tim,

starting with ELOG version 3 all entries are moved into sub-directories for each year.

If you move the files back
from the sub-directories and restart elogd, then the entries should appear again in the logbook with ELOG 2.9.2.

 

I don't
know how to solve your other problem. Maybe you should talk to someone locally who can administer your windows server?

Cheers, Andreas

 

    icon2.gif   Re: Width of text field, posted by Andreas Luedeke on Wed Mar 23 11:40:52 2016 
Did you try the options


Summary lines = x
Summary line length = x


as
documented in https://midas.psi.ch/elog/config.html#flags ?
ELOG V3.1.5-3fb85fa6