Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Stefan Ritt on Wed Oct 11 08:18:14 2006
|
[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 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]
|
Option to require new user registration to subscribe to ALL logbooks, posted by Steve Jones on Mon Nov 6 19:03:11 2006
|
Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would like to limit this
to the "admin" user to pick per individual.
|
|
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]
|
|
Re: Option to require new user registration to subscribe to ALL logbooks, posted by Stefan Ritt on Thu Nov 9 22:57:38 2006
|
[quote="Steve Jones"]Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can register with? I would
like to limit this to the "admin" user to pick per individual.[/quote]
|
|
Re: Option to require new user registration to subscribe to ALL logbooks, posted by Steve Jones on Thu Nov 9 23:37:37 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]Stefan, any chance of having an option that eliminates the ability of new users to pick the logbooks they can
register with? I would like to limit this to the "admin" user to pick per individual.[/quote]
|