Q: On Solaris 8, eLog not honoring USR= and GRP= cfg file directives?, posted by Steve Jones on Wed Aug 11 18:12:35 2004
|
I'm not sure if this is a configuration problem or a bug, but running
v2.5.4subver1.413, elogd runs as user ROOT (UID0) even though the following
is in the elogd.cfd file:
|
Re: Q: On Solaris 8, eLog not honoring USR= and GRP= cfg file directives?, posted by Stefan Ritt on Thu Aug 12 21:37:29 2004
|
> I'm not sure if this is a configuration problem or a bug, but running
> v2.5.4subver1.413, elogd runs as user ROOT (UID0) even though the following
> is in the elogd.cfd file:
|
Re: Q: On Solaris 8, eLog not honoring USR= and GRP= cfg file directives?, posted by Steve Jones on Thu Aug 12 22:18:56 2004
|
> > I'm not sure if this is a configuration problem or a bug, but running
> > v2.5.4subver1.413, elogd runs as user ROOT (UID0) even though the following
> > is in the elogd.cfd file:
|
Re: Q: On Solaris 8, eLog not honoring USR= and GRP= cfg file directives?, posted by Stefan Ritt on Thu Aug 12 22:25:45 2004
|
> Just for grins, what version of compiler are you using under Linux?
gcc 3.2.2 (from RedHat Linux 9.0) |
Re: Q: On Solaris 8, eLog not honoring USR= and GRP= cfg file directives?, posted by Steve Jones on Mon Aug 16 21:48:49 2004
|
> > Just for grins, what version of compiler are you using under Linux?
>
> gcc 3.2.2 (from RedHat Linux 9.0)
|
Restricting viewing messages, posted by Jen Manz on Wed Aug 11 15:38:07 2004
|
I am working on a logbook for a lab. I have two questions...
First - Some of the logbook entries should not be viewed by certain users.
What would be the easiest way to restrict viewing some entries?
|
Re: Restricting viewing messages, posted by Stefan Ritt on Wed Aug 11 16:02:52 2004
|
> First - Some of the logbook entries should not be viewed by certain users.
> What would be the easiest way to restrict viewing some entries?
|
THREAD DISPLAY = sucks up coded spaces, posted by Steve Jones on Fri Aug 6 22:35:10 2004
|
I was trying to do some hard coded spaces using:
Thread display = For: $Date for Shutdown. $DataCenter:
|
Re: THREAD DISPLAY = sucks up coded spaces, posted by Stefan Ritt on Sun Aug 8 16:25:09 2004
|
> I was trying to do some hard coded spaces using:
>
> Thread display = For: $Date for Shutdown. $DataCenter:
|
Re: THREAD DISPLAY = sucks up coded spaces, posted by Steve Jones on Tue Aug 10 20:11:38 2004
|
> > I was trying to do some hard coded spaces using:
> >
> > Thread display = For: $Date for Shutdown. $DataCenter:
|
Login/Logout problem with elog and their solution, posted by Stefan Ritt on Thu Aug 5 10:49:21 2004
|
Hi everybody,
several people have reported of strange problems concering the login/logout
|
User/Admin privlege question, posted by Ralph Kuehn on Thu May 20 00:55:51 2004
|
Hello,
For some reason if I define a "login user" that is allowed the configure
|
Re: User/Admin privlege question, posted by Stefan Ritt on Fri May 21 14:43:09 2004
|
> For some reason if I define a "login user" that is allowed the configure
> option he is also allowed to change the configuration file. According to the
> documentation it seems like this should NOT be the case. Any ideas as to
|
Re: User/Admin privlege question, posted by Alexandre Camsonne on Fri Jul 2 15:18:20 2004
|
Hi,
I also have this problem, when a non admin user logs in he does not have access to
the config file but if he logs out he can then access the config file as non logged
|
Re: User/Admin privlege question, posted by Stefan Ritt on Wed Jul 7 17:43:22 2004
|
> I also have this problem, when a non admin user logs in he does not have access to
> the config file but if he logs out he can then access the config file as non logged
> user.
|
Re: User/Admin privlege question, posted by Alexandre Camsonne on Tue Aug 3 05:31:08 2004
|
Dear Stefan,
I eventually tried the latest version from the CVS.
And it is odd because like when I tried version 2.5.3, it is like it ignores
|
Re: User/Admin privlege question, posted by Stefan Ritt on Tue Aug 3 12:46:55 2004
|
I just see your [global] part of elogd.cfg, could you send me the complete file?
What you also could try is to delete all cookies stored in your browser. The way
|
Re: User/Admin privlege question, posted by Alexandre Camsonne on Tue Aug 3 14:51:34 2004
|
The elogd.cfg is attached in the previous message as attachement 3. Sorry it is a
little bit buried between pictures.
The reason I put the picture of the global elogd.cfg is to show that the not logged
|
Re: User/Admin privlege question, posted by Stefan Ritt on Tue Aug 3 16:34:23 2004
|
Ok, now I see your problem. You defined a "Guest menu commands" which explicitly allows
not-authorized access (that's what it's for). If you only want to allow authorized
access, remove the "guest menu commands" from the logbook sections and also from the
|
Re: User/Admin privlege question, posted by Alexandre Camsonne on Tue Aug 3 20:14:55 2004
|
Thank you, I misunderstood how the "Guest menu commands" worked I thought I had to specify
a limited set of commands to actually limit guest users.
|
speeding up elog : gcc compile optimizations, posted by Fred Hooper on Tue Jul 27 18:33:52 2004
|
Elog is a great program, but it can be slow.
I noticed that the gcc compiler options in the tarball Makefile were not
|
Re: speeding up elog : gcc compile optimizations, posted by Stefan Ritt on Wed Jul 28 15:03:17 2004
|
> I noticed that the gcc compiler options in the tarball Makefile were not
> conducive to speed. There, I tried changing the gcc options to:
>
|
Re: speeding up elog : gcc compile optimizations, posted by Fred Hooper on Sat Jul 31 16:55:21 2004
|
> > I noticed that the gcc compiler options in the tarball Makefile were not
> > conducive to speed. There, I tried changing the gcc options to:
> >
|
Re: speeding up elog : gcc compile optimizations, posted by Stefan Ritt on Mon Aug 2 09:05:48 2004
|
> Is there something else which is making this difficult to do?
Not really, but hsearch() & Co. are not available under Windows, so I have to extract the
|
Re: speeding up elog : gcc compile optimizations, posted by Drew on Tue Aug 3 16:59:36 2004
|
> > Is there something else which is making this difficult to do?
>
> Not really, but hsearch() & Co. are not available under Windows, so I have to extract the
|
curly parenthesis problem , posted by Heiko Scheit on Tue Aug 3 15:44:07 2004
|
Everything after curly parenthesis is ignored in attribute entry boxes
like 'Subject' above
|
Re: curly parenthesis problem {smiley}, posted by Stefan Ritt on Tue Aug 3 16:18:45 2004
|
> Everything after curly parenthesis is ignored in attribute entry boxes
> like 'Subject' above
>
|
Wishlist: TOOLTIP for ATTRIBUTES, posted by Steve Jones on Wed Jul 14 21:47:47 2004
|
Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
For a complex entry form it is desireable to try and have everything in a
|
Re: Wishlist: TOOLTIP for ATTRIBUTES, posted by Stefan Ritt on Wed Jul 14 22:21:55 2004
|
> Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
|
Re: Wishlist: TOOLTIP for ATTRIBUTES, posted by Steve Jones on Wed Jul 14 22:54:43 2004
|
> > Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> > is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
>
|
Re: Wishlist: TOOLTIP for ATTRIBUTES, posted by Stefan Ritt on Thu Jul 15 10:01:03 2004
|
Ok, I added the option
Tooltip <attribute> = ...
|
Re: Wishlist: TOOLTIP for ATTRIBUTES, posted by Steve Jones on Mon Aug 2 19:27:56 2004
|
> Ok, I added the option
>
> Tooltip <attribute> = ...
|