Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 589 of 808  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  66251   Mon Mar 16 22:33:23 2009 Idea Dongwook Jangdwjang@fnal.govRequestLinux2.7.5-2130Adding texts for each attachment

Dear Stefan,

First of all, I appreciate that you made such a nice program. I've used elog for more than 5 years and it was wonderful experince to me and my research work was very productive with this.

I have a suggestion to you to improve this while I was using elog. If users can add texts or comments for each attachment, it will be great.

I am not sure if someone was already suggested this or it is already in your wish list.

Thank you.

Dongwook Jang

  66253   Tue Mar 17 02:05:08 2009 Reply Dongwook Jangdwjang@fnal.govRequestLinux2.7.5-2130Re: Adding texts for each attachment

Stefan Ritt wrote:

 

Dongwook Jang wrote:

Dear Stefan,

First of all, I appreciate that you made such a nice program. I've used elog for more than 5 years and it was wonderful experince to me and my research work was very productive with this.

I have a suggestion to you to improve this while I was using elog. If users can add texts or comments for each attachment, it will be great.

I am not sure if someone was already suggested this or it is already in your wish list.

Thank you.

Dongwook Jang

 

Dear Dongwook,

no, this is not implemented and also was never requested. The way most people work is that images are included directly in the text, and the the text goes along with that.

So for example if I want to show you the ELOG logo, I put it here: elog.png 

If I want to add a comment for an attachment, I write it in the text and just refence the attachment with link. This way is more flexible that adding just a line of text to each attachment, since you can write several lines in the text, make a table etc. etc.

 

 

Dear Stefan,

Maybe I used elog with very inefficient way so far. The way you suggested requires putting figures somewhere else, right?

Elog saves attachments on the machine that elog is running. I want to store figures in elog.

The logo you showed above is stored in this entry?

Thank you.

Dongwook Jang

  66332   Tue Apr 28 21:25:31 2009 Question Dongwook Jangdwjang@fnal.govQuestionLinux2.7.6elogd runs by a user but not by root

Hi,

I really don't understand why elogd cannot run by root but it runs by a user.

I've put elog deamon in /etc/init.d. So it didn't bring up, but it runs if I run it by user interactively.

Thanks,

Dongwook

  66335   Wed Apr 29 18:20:38 2009 Reply Dongwook Jangdwjang@fnal.govQuestionLinux2.7.6Re: elogd runs by a user but not by root

Stefan Ritt wrote:

 

Dongwook Jang wrote:

Hi,

I really don't understand why elogd cannot run by root but it runs by a user.

I've put elog deamon in /etc/init.d. So it didn't bring up, but it runs if I run it by user interactively.

Thanks,

Dongwook

 

That's a security issue. If elogd runs under a user and gets hacked, the hacker obtains just the user rights, which can be limited. If it runs under root, the hacker will automatically get root rights, which is bad. Technically, there is no reason why elogd cannot be run as root. Just put

Usr = root

Grp = root

into elogd.cfg. 

 Hi,

I wonder how others manage this situation because deamons in /etc/init.d is excercuted by root. So I cannot run in /etc/init.d/elogd when the system starts up.

What do you think?

Thanks,

Dongwook

  66338   Thu Apr 30 20:49:03 2009 Reply Dongwook Jangdwjang@fnal.govQuestionLinux2.7.6Re: elogd runs by a user but not by root

Stefan Ritt wrote:
Dongwook Jang wrote:

 Hi,

I wonder how others manage this situation because deamons in /etc/init.d is excercuted by root. So I cannot run in /etc/init.d/elogd when the system starts up.

What do you think?

Thanks,

Dongwook

The normal situation is that elogd gets started by root under /etc/init.d/, then the configuration file contains "Usr = elog" and "Grp = elog", so after it has been started as root, the program falls back to the "elog" user, which only has restricted rights. 

 

 

Now I realized that it is not a problem in /etc/init.d, but deamon itself.

When I run the following command as a root, it didn't run

/mnt/wd500/jnj/products/elog/sbin/elogd -D -c /mnt/wd500/jnj/products/elog/elog/elogd.cfg

But, it runs when I did as a user.

I really don't understand this strange behavior.

Thanks,

  69104   Fri Jan 31 18:22:50 2020 Question Duarte Alexandre Vicente Paisduarte.pais@psi.chQuestionWindowselog-latestRunning ELOG as daemon in Windows not working

Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other machine. I tried to search in this forum, but with no avail.

Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG?

Cheers,

Duarte

  69106   Fri Jan 31 19:26:51 2020 Reply Duarte Alexandre Vicente Paisduarte.pais@psi.chQuestionWindowselog-latestRe: Running ELOG as daemon in Windows not working

Do you know which settings in the firewall panel I should change (windows 10 machine)? I went over all the access rules and could not find anything corresponding to the ELOG.

Duarte

Stefan Ritt wrote:

Probably a problem with your Windows Firewall. You have to convice your OS to let you in.

Stefan

Duarte Alexandre Vicente Pais wrote:

Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other machine. I tried to search in this forum, but with no avail.

Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG?

Cheers,

Duarte

 

 

  2033   Thu Nov 2 18:02:44 2006 Warning David Spindlerdsspindler@gmail.comBug reportWindows2.6.2-1734Bug? Password file location changed
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different location.

I have a password file called pwd.txt. It resides in the main elog directory, in my case, c:\elog, along with the elgod.exe and elogd.cfg. Apparently, the new version looks for it in the logbooks directory. I adjusted my path to the file and it works fine.

I am reporting this as a bug because it is my guess that this is not an expected result. I would expect the old elogd.cfg file to work without altering in the newer version.

Thanks, keep up the great work, Stefan. You have a great program.
David Spindler
ELOG V3.1.5-3fb85fa6