ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
Text |
 |
484
|
Fri Feb 27 10:28:00 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 2.5.1 | Re: Default Sorting Option | This can be easily achieved with the configuration
option
|
|
483
|
Fri Feb 27 10:09:04 2004 |
| Ulrich TrĂ¼ssel | ulrich.truessel@familienhund.ch | Question | Linux | Windows | 2.5.1 | Default Sorting Option | I really don't know if anybody already had
this problem or i just didn't
find the solution in the documenttaion: |
|
482
|
Fri Feb 27 09:15:07 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5 | Re: Instant Edit Link | I have added that functionality according
to your request. In elogd.cfg, you
can specify
|
|
481
|
Fri Feb 27 03:48:05 2004 |
| Raj | Elog+rajelio@yahoo.com | Question | Windows | 2.5 | Instant Edit Link | How I can dynamically create a link when a
new submission is entered that
will have a value of <ELOG_URL$message id?=Edit>
|
|
480
|
Thu Feb 19 09:38:13 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.0 | Re: elogd does not exit on SIGTERM | Noee. Here it works immediately.
Can you try with a fresh server from the |
|
479
|
Wed Feb 18 16:54:27 2004 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.0 | elogd does not exit on SIGTERM | When trying to stop elogd processes with the
kill command
elogd exits only after access to the logbook.
|
|
478
|
Mon Feb 16 17:18:39 2004 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | | Linux | 2.5.0 | Re: -W -Wall options (using gcc) | > > Have a look at the gcc info pages:
> >
> > $ info gcc "invoking gcc" "warning options"
|
|
477
|
Mon Feb 16 16:47:55 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | | Linux | 2.5.0 | Re: -W -Wall options (using gcc) | > Have a look at the gcc info pages:
>
> $ info gcc "invoking gcc" "warning options"
|
|