| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66335
|
Wed Apr 29 18:20:38 2009 |
 | Dongwook Jang | dwjang@fnal.gov | Question | Linux | 2.7.6 | Re: 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 |
| Dongwook Jang | dwjang@fnal.gov | Question | Linux | 2.7.6 | Re: 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 |
 | Duarte Alexandre Vicente Pais | duarte.pais@psi.ch | Question | Windows | elog-latest | Running 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 |
| Duarte Alexandre Vicente Pais | duarte.pais@psi.ch | Question | Windows | elog-latest | Re: 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 |
 | David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Bug? 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 |
|
2034
|
Thu Nov 2 18:10:07 2006 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Re: Bug? Password file location changed |
| David Spindler wrote: | 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 |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
|
2039
|
Fri Nov 3 14:40:36 2006 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.6.2-1734 | Re: Bug? Password file location changed |
| Steve Jones wrote: |
| David Spindler wrote: |
| David Spindler wrote: | 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 |
I also just noticed that the text files I use for presetting the text window also have to be in the logbooks directory. |
| Quote: | The relocation was a documented change that Stefan made intentionally. Yes, it caught me too  |
|
Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks! |
|
66571
|
Mon Nov 2 21:23:38 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 | I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
Thanks,
David |
|