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 ?
|
|
68258
|
Wed Feb 10 22:55:42 2016 |
| Diego | diego.obradors@ciemat.es | Question | Windows | 3.1 | size of atributes in summary mode |
Good night,
I would be grateful if someone could indicate me, how could I increase the size of the block where the text of the atribute are in the summary mode.I would like, for example, increase the size of the "subject" you can see on the picture.
Thank you so much!!!
|
68259
|
Wed Feb 10 23:44:38 2016 |
| Diego | diego.obradors@ciemat.es | Question | Windows | 3.1 | Re: size of atributes in summary mode |
I answer myself... Modify the value of width=100% in the class .listtitle2 in the .css file.
Diego wrote: |
Good night,
I would be grateful if someone could indicate me, how could I increase the size of the block where the text of the atribute are in the summary mode.I would like, for example, increase the size of the "subject" you can see on the picture.
Thank you so much!!!
|
|
68264
|
Tue Feb 23 22:32:30 2016 |
| Jimmy Bria | jimmy.bria@gmail.com | Question | Linux | 3.0.0 | Re: Kerberos auth not available on 3.0 ? |
Hi Stefan - Do you know is Kerberos is available (compiled) on the Windows installer?
-Jimmy
Stefan Ritt wrote: |
Kerberos support is not compiled into the binary RPM. You have to comile from sources to get that. The reason is that there are different Kerberos libraries around, and different people need different ones.
/Stefan
|
|
68265
|
Wed Feb 24 09:48:09 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.0.0 | Re: Kerberos auth not available on 3.0 ? |
Hi Jimmy, no Kerberos is not compiled into the Windows installer. You are the first one asking for that under Windows. All other Kerberos users use Linux so far. You have to compile the Windows version yourelf. This is because there are several versions of Kerberos around and people need differnt libraries. Sorry for that.
/Stefan
Jimmy Bria wrote: |
Hi Stefan - Do you know is Kerberos is available (compiled) on the Windows installer?
-Jimmy
Stefan Ritt wrote: |
Kerberos support is not compiled into the binary RPM. You have to comile from sources to get that. The reason is that there are different Kerberos libraries around, and different people need different ones.
/Stefan
|
|
|