Options Items limits, posted by Patricio Castro on Tue Aug 31 20:29:20 2004
|
Hello friends,
Exist some form to increase limits of items (100) in the Options List
|
Re: Options Items limits, posted by Steve Jones on Wed Sep 1 22:25:01 2004
|
> Hello friends,
>
> Exist some form to increase limits of items (100) in the Options List
|
Re: Options Items limits, posted by Stefan Ritt on Tue Sep 7 17:49:50 2004
|
> > Hello friends,
> >
> > Exist some form to increase limits of items (100) in the Options List
|
|
PostScript Files shown as text., posted by Bryan Moffit on Fri Sep 3 20:17:20 2004
|
At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog. Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).
|
|
PostScipt Files shown as text., posted by Bryan Moffit on Fri Sep 3 20:17:12 2004
|
At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog. Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).
|
|
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.
|