ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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 distribution, with the example
elogd.cfg, to see if there is any difference?
The killing is handled in the funciton ctrlc_handler(), which sets _abort =
TRUE. This is checked in line 16195, just after the select(), and the main
loop is exited. The select finishes after one second, although I believe
that the kill signal also terminates the select prematurely. The kill
command and a Ctrl-C keystroke should work the same way, they both generate
a SIGTERM or SIGINT signal. |
486
|
Sat Feb 28 16:46:41 2004 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Bug report | | 2.5.1 | System Error / Hangs with ELPG and threaded Msg's under Win 2k3 Server |
Since I'n not a programmer I's like to be very carefulls with bug
reports, but after testing for a while, I belive this my be a bug or
something else:
I have 2 systems running ELOG 2.5.1:
1. uSE Linux 8.2, KDE 3.2 = NO problems at all! ELOG work's in every
function quiet well!
2. The Internet Server (of my friend): Windows 2003 Server, All MS paches
installed, Running IIS 6.0 Port 80) and ELOG 2.5.1 (Port 8080) under
FireDeamon 1.6GA (actual release) as a Service (Deamon).
Problem under Win 2k3:
This works very well, even with several users on the system and on ELOG
as long as there is not msg. threaded! Is a Msg. Treaded ELOG produces
the msg. showen in the attached Jepg-file below on Win 2k3.
The problem occurs as soon as Elog would change to the threaded display
or by clicking "Repaly" in the menu. Rights etc. are aleady checked on
the file system and are looking well. Everithing will work well as
nothing is thraded or testing locally under Linunx.
Does anybody
have an idea??? It my by a bog on Elog as well as from Microsoft or a
problem produced by a dummy user (me...!). Since Linux don't have the
problem and the same cfg-file and log-files are working well if I don't
use mode=threaded as well as Display mode = threaded I believe it my be a
realchance not to be the personal factor of the dummy user...
ThankX for every hint!
|
Attachment 1: Replay_Error_ELOG_auf_Wind_2k3_Server.jpg
|
|
557
|
Fri Jun 4 22:40:44 2004 |
| Robin Peterson | robin.h.peterson@state.or.us | | | 2.52 | Using select menu option to move multiple logbook entries to another logbook |
I'm trying to configure this thing to be able to filter on a set of
criteria, choose select, choose toggle all, and then choose "Move to
Complete Work Requests".
I've been able to select a specific logbook entry and move it, and I've
been able to filter and select and toggle, but I can't figure out how to
get the Move To option to show up on the main logbook menu....
what am I missing?
robin |
653
|
Tue Aug 3 16:59:36 2004 |
| Drew | drew.card@gmail.com | Bug fix | Linux | Windows | 2.5.3 | Re: speeding up elog : gcc compile optimizations |
> > 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
> source code from the GNU C libarary or so. Since the last discussion I had lots of other
> topics on my to-do list, such as mirroring and cloning, but the speed issue is getting more
> and more up on the priority list.
Speaking of windows I'd like to note that when I moved my call tracking config from a slow BSD
system (PPro 200Mhz) to a faster windows system (P3 733M) I noted a huge slow down in the
interface. Talking about perhaps 1-2 seconds before to 10-15 seconds after. Using
sysinternals file monitor I see that elogd is hammering each log file in the directory. Not
sure what else is going on. 309 log files - only 1.25Meg.
Anything I can do short of pruning down the files?
[Edit: In both cases above my default view is filtered and sorted - so that I only see things
with a specific status. Taking away the filtering resolves this hit - but does not explain the
speed difference between platforms.]
-D |
678
|
Fri Aug 27 00:49:27 2004 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | 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 distribution, with the example
> elogd.cfg, to see if there is any difference?
>
> The killing is handled in the funciton ctrlc_handler(), which sets _abort =
> TRUE. This is checked in line 16195, just after the select(), and the main
> loop is exited. The select finishes after one second, although I believe
> that the kill signal also terminates the select prematurely. The kill
> command and a Ctrl-C keystroke should work the same way, they both generate
> a SIGTERM or SIGINT signal.
elogd does not exit if there is an 'unprocessed' HUP. So when you do
kill -HUP <pid>
kill <pid>
elogd will only exit after it was accessed. |
821
|
Fri Dec 3 08:43:49 2004 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Bug report | Windows | 2.5.5-1 | ELOG-Server crashes after date entry |
God really STRANGE and problematic effect on 2.5.5-1 (can't remember it this
was with 2.5.5 or 2.5.4-X but i'm nearly sure it worked well):
Entering a date (Formate Bithday = date) may crash down the server:
Value is 22.2.2004: Everything is well
Value is 22.2.1962: Server crashes emmediatly (menas restarzing several
times, always the same problem)
I do not have time to check true all the years for finding out where the
problem may beginn, sorry. Also I was not able to check on other systems
right now. My system: Win XP Pro SP 1, IE 6 as well as Mozilla Calssic 1.7.3.
Didn't check it under Linux right know in case of a lot work.
Clould you this fix please Stefan??? THANK'X!!! |
949
|
Wed Feb 16 08:58:47 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | Linux | 2.5.6 | Re: images attached shown as inline |
> > the following should do the job:
> >
> > <div style="width: 200px">
> > <img src="IMG_3133.jpg" style="width: 100%" />
> > </div>
> >
> > the configurable parameter should be with obviously :-)
>
> Unfortunately not. Please find attached the screen dump from such a try, together with the HTML code.
> As you can see, the little elog icon is stretched to the same width as the upper (large) picture.
you are right ;-( I used a different code in my test and sent you and old test code, *but* also the last
one does not works on every browser ... the following code would do the job, but it seems to work only
in gecko-based browsers such as mozilla, firefox and safari ...
<div style="width: 200px">
<img src="IMG_3133.jpg" style="max-width: 200" />
</div>
other browsers do not scale the vertical dimention :-( |
1008
|
Thu Mar 24 10:31:01 2005 |
| Stephen A. Wood | saw@jlab.org | Bug report | Linux | | Crash with Protect Selection page = 1 |
Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
as soon as it is accessed.
Under 2.5.7, a login page will come up, and the logbook will work, but only
if a valid username/password is given. If an invalid login is given, then
elogd crashes. We have a cron job that periodically restarts elogd if it is
has crashed.
Steve
[global]
logbook tabs = 0
port = 8080
Protect Selection page = 1
Password file = user.info
Admin user = saw
|