ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1013
|
Thu Mar 24 11:28:13 2005 |
| Stephen A. Wood | saw@jlab.org | Bug report | Linux | | Re: 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.
>
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
>
> - Stefan
That was fast! I put the elogd.c from the cvs on top of 2.5.8 and now I can run
the server with Protect Selection page=1 again.
Logins work OK if the username/password is valid. However, if I try to login
with invalid authentication, the server crashes. If I turn off the protect
selection page, then invalid authentication does not crash elogd.
Thanks, Steve |
1015
|
Thu Mar 24 12:09:55 2005 |
| Stephen A. Wood | saw@jlab.org | Bug report | Linux | | Re: Crash with Protect Selection page = 1 |
> > Logins work OK if the username/password is valid. However, if I try to login
> > with invalid authentication, the server crashes. If I turn off the protect
> > selection page, then invalid authentication does not crash elogd.
>
> Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
>
> I fixed that as well and committed the changes.
That seems to do the trick! Thanks, Steve |
1098
|
Mon Apr 18 17:02:20 2005 |
| Stephen A. Wood | saw@jlab.org | | Linux | 2.5.8-3 | Directories in top groups |
I am trying to unify several existing logbook collections that run on
seperate servers under a single server using groups. For a top group, under
"[global topgroupname]", I would like to redefine the resource directory or
the logbook directory so that everything except for the .cfg is at it
original location. However, it seems like "Resource dir" and "Logbook dir"
can not be redefined in the global section for specific groups. Is it
possible to redefine these directories for each top group, or is it feature
that could be added?
I could probably do what I want with soft-links, but redefining the resource
dir just seems to be right way to do this. (For one thing, I would like
different favicons for each group.) |
1102
|
Tue Apr 19 22:43:10 2005 |
| Stephen A. Wood | saw@jlab.org | Question | Linux | 1.632 | More questions about groups |
I am running 2.5.8-3 with the elogd.c 1.632. I have attached the config
file that I am using. I have a top group "src", with logbooks "SRC
Analysis" and "SRC Mail" in it. These two logbooks share the same password
file. If one logs into one, I would like them to be not have to login to
the other. If I put the password file name under [global src], I get this
behaviour, but the logbook selection page does not show my graphic or the
locks by the logbook names (instead it has the Alt text "This logbook
requires authentication." If I remove the password from [global src] and
put it in each logbook individually, then my logbook selection page looks
OK, but I have to log into each logbook seperately.
Stephen |
1104
|
Fri Apr 22 18:16:25 2005 |
| Stephen A. Wood | saw@jlab.org | Question | Linux | 1.632 | Re: More questions about groups |
> Thanks for reporting this bug. I fixed it in the current CVS version.
I get my Icons and Graphics in the top group now. Thanks for fixing it. |
1823
|
Mon May 8 18:23:17 2006 |
| Stephen A. Wood | saw@jlab.org | Request | Linux | | Spec file change |
Could the "Copyright:" line in the elog.spec file be changed to "License:" for the next release? Without this change an RPM can't be built on FC4 (RPM 4.4.1). With the change, rpms can still be built in Enterprise linux 3 (RPM 4.2.3). |
67628
|
Tue Nov 26 16:24:39 2013 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Crash report involving propagate and replies |
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option? |
67630
|
Wed Nov 27 15:22:37 2013 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
David Pilgram wrote: |
Stephen wrote: |
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Hi Stephen,
I see that you don't allow branching in your threads. Why do you need to propagate the Status throughtout the thread? Why not just mark the latest entry and (incase it is necessary) 'collapse to last = 1'
I'm not saying that the bug (if bug it is, rather than a preset limitation) you've found should not be fixed, but I'm puzzled as to why you happen to use the feature. I can see the point if an initial entry provides a whole tree of branches (and a limit of 10 is rather limiting). OK, I know if it is historic, it cannot easily be changed because of other users. Or if some users will primarily be responding to emails rather viewing the logbook via a browser. I'm a single (ab)user elog system myself, so I'm very tolerant of changing how elog works if it offers an improvement.
|
Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing. Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case. Even with branches the system will crash once there are 10 replies in the note with propagate on.
As for use case, with a few users I needed a way to represent a note as open so that the next person knew work still needed to be done. Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max). I will experiment with the collapse to last to see how it looks. Any other suggestions would be helpful. |