Scroll box for attributes, posted by mo on Tue Jul 30 17:33:24 2002
|
Hello,
If you have the text box turned off so you only enter attributes, is it
possible to have a couple of attributes that have small scroll through text
|
Sample of actual elog Config with URL in SSL, posted by Dawang on Mon Dec 14 04:42:04 2015
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial /
guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1? |
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Thu Oct 26 21:54:40 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but
the the non-daemn mode also sets to nobody and works fine.[/QUOTE]
|
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Stefan Ritt on Wed Nov 8 08:20:34 2006
|
[quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings common to all logbooks[/CODE]
is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking
"[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Wed Nov 8 12:55:58 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings
common to all logbooks[/CODE] is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup
the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode, posted by Stefan Ritt on Wed Nov 8 13:07:31 2006
|
[quote="Steve Jones"]Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately
after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.[/quote]
|
SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Mon Sep 18 20:35:44 2006 
|
On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely
where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root,
simply one with and one without the "-D" |
|
SSL does not work, posted by Hisataka YOSHIDA on Fri Jun 5 03:49:20 2020
|
Hello.
I installed the latest elog (3.1.4-2) in CentOS 7, and it is working well without SSL.
When I enalbled SSL option (SSL = 1) in the "elogd.cfg", and tried to start the elogd, the message below was shown and failed to run. |