Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Wed Aug 11 18:02:22 2004
|
The help text on the website says the following:
"The command Select can be used to select multiple messages for deletion of
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Thu Aug 12 21:10:29 2004
|
> The help text on the website says the following:
>
> "The command Select can be used to select multiple messages for deletion of
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Thu Aug 12 22:17:01 2004
|
> > The help text on the website says the following:
> >
> > "The command Select can be used to select multiple messages for deletion of
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Thu Aug 12 22:24:04 2004 
|
> Thank you. I had added the "Move To" and this works at the log entry
level (i.e., "Move
> To <name>) but in the threaded view one does not get the enumerated list
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Thu Aug 12 23:55:00 2004
|
> > Thank you. I had added the "Move To" and this works at the log entry
> level (i.e., "Move
> > To <name>) but in the threaded view one does not get the enumerated list
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Wed Sep 8 11:44:56 2004
|
> Hmmm. I like the little buttons with the pull-downs for selections.
> Unfortunately, I don't get that. With a config of:
>
|
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
|