ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68254
|
Mon Feb 8 16:19:11 2016 |
| Tapasi Ghosh | tapasi03@gmail.com | Question | Mac OSX | elog-3.1.0 | Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/" |
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/
ls -ltr
drwxrwxrwx 6 tapasi admin 204 Jan 7 18:26 demo
Andreas Luedeke wrote: |
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")
Cheers, Andreas
Tapasi Ghosh wrote: |
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
68255
|
Mon Feb 8 16:27:45 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Mac OSX | elog-3.1.0 | Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/" |
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
Tapasi Ghosh wrote: |
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/
ls -ltr
drwxrwxrwx 6 tapasi admin 204 Jan 7 18:26 demo
Andreas Luedeke wrote: |
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")
Cheers, Andreas
Tapasi Ghosh wrote: |
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
|
68256
|
Mon Feb 8 17:40:27 2016 |
| Tapasi Ghosh | tapasi03@gmail.com | Question | Mac OSX | elog-3.1.0 | Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/" |
Sorry, it was my mistake while copying from terminal to the email . There is no "demo" directory under /usr/local/lib.
Tapasis-MacBook-Pro:elog tapasi$ cd /usr/local/elog/logbooks/demo
Tapasis-MacBook-Pro:demo tapasi$ ls -ltr
total 0
drwxr-xr-x 3 tapasi admin 102 Sep 22 11:00 2001
drwxr-xr-x 55 503 admin 1870 Dec 17 13:21 2015
drwxr-xr-x 2 tapasi admin 68 Jan 7 14:54 2016
So, how can I change the user from "nobody" to my name, so that elogd runs in my user name ?
Thanks
Andreas Luedeke wrote: |
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
Tapasi Ghosh wrote: |
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/
ls -ltr
drwxrwxrwx 6 tapasi admin 204 Jan 7 18:26 demo
Andreas Luedeke wrote: |
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")
Cheers, Andreas
Tapasi Ghosh wrote: |
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
|
|
68257
|
Mon Feb 8 19:29:47 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Mac OSX | elog-3.1.0 | Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/" |
Use
usr = <user anme>
in elogd.cfg as written in the documentation.
Stefan
Tapasi Ghosh wrote: |
So, how can I change the user from "nobody" to my name, so that elogd runs in my user name ?
|
|
67691
|
Tue Jul 29 16:53:18 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: New entries remotely? |
Daniel Roldan wrote: |
Hi all,
I would like to create a new entry remotely.
I would like that when the macro run, the macro automatically create a new entry in my Elog.
I was searching, but i don't saw any thing about this.
Is possible to do a new entry remotely?
Thanks for all.
|
Use the "elog" command line utility as described here under tips & tricks: http://midas.psi.ch/elog/userguide.html |
66995
|
Thu Jan 20 08:52:43 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.8.0 | Re: New entries are not visible from other logbooks based on the same logbook dir through Subdir |
JacekK wrote: |
Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new entry in one logbook, then that entry is not visible in other logbook.
I suppose it is a bug in el_submit function, where I think the new message should be added to message index of every logbook based on the same data directory as the one, where the message was physically created.
There is a piece of code, which I think should do this automatically
/* if other logbook has same index, update pointers */
but it seems the other logbooks does not have the same index.
I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.
Let me know is this bug possible to fix in near future.
Best regards,
Jacek
|
Well, having two logbooks in the same subdirectory was initially a planned feature but really never worked. I re-visited this issue and made it working in the current SVN version. So the next release will contain the fix. |
69645
|
Fri Feb 3 20:26:46 2023 |
| Antonio Bulgheroni | Looking antonio.bulgheroni@gmail.com | Info | Linux | Mac OSX | 3.1.5 | Re: New elog version 3.1.5 |
Looking forward to the windows installer.
Thanks a lot and keep up the good work!
cheers,
toto
Stefan Ritt wrote: |
A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.
https://elog.psi.ch/elog/download.html
Best,
Stefan
|
|
69663
|
Tue Apr 11 12:51:12 2023 |
| Finn Junker | Hi fj@tvis.net | Info | Linux | Mac OSX | 3.1.5 | Re: New elog version 3.1.5 |
Hi Stefan
Is there anything the community or forum can help you with or supply for creating a windows version?
Kind Regards Finn
Stefan Ritt wrote: |
A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.
https://elog.psi.ch/elog/download.html
Best,
Stefan
|
|