Re: New password file problem, posted by Stefan Ritt on Wed Nov 24 15:14:29 2010
|
Mariusz Stakowski wrote:
Hello, |
Re: New password file problem, posted by Mariusz Stakowski on Wed Dec 1 17:03:01 2010
|
Stefan Ritt wrote:
|
|
Re: New feature request for Options list, posted by Stefan Ritt on Wed Feb 20 22:45:39 2019
|
I can put it on the wish list.
Alan
Grant wrote:
Is it possible to include an option in the next release to have the |
|
Re: New feature request for Options list, posted by Andreas Luedeke on Thu Feb 28 14:56:50 2019
|
Just my two cent - I would have many very good applications for that feature:
Keep option lists identical over different logbooks.
Keep option lists identical over different applications.
Create
option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, |
|
Re: New feature request for Options list, posted by David Pilgram on Thu Feb 28 16:03:36 2019
|
May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).
I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.
Clunkey and binned. |
|
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") |
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 16:19:11 2016
|
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/ |
|
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 |