| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
504
|
Wed Mar 10 06:56:19 2004 |
 | Raj | rajelio@yahoo.com | Bug report | | 2.5.1 | Re: System Error / Hangs with ELOG and threaded Msg's under Win 2k3 Server | Run into the same error on a windows XP & 2000 machine. Totally shuts down the elogd.exe
when THREADED is selected. Have not tried your modified version after reading the posted
results. Will run with summary view until fixed. Wish I could help but I'm not a
programmer. Let me know if you want to test any new elogd.exe's. |
|
505
|
Tue Mar 16 09:50:58 2004 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | | 2.5.1 | Re: System Error / Hangs with ELOG and threaded Msg's under Win 2k3 Server | > Run into the same error on a windows XP & 2000 machine. Totally shuts down the elogd.exe
> when THREADED is selected. Have not tried your modified version after reading the posted
> results. Will run with summary view until fixed. Wish I could help but I'm not a
> programmer. Let me know if you want to test any new elogd.exe's.
This problem has been fixed now, it was a programming bug. New version under
http://midas.psi.ch/elog/download/windows/elogd.exe |
|
506
|
Tue Mar 16 20:27:56 2004 |
 | Ulrich Trüssel | ulrich.truessel@familienhund.ch | Bug report | Windows | 2.5.1 | Re: System Error / Hangs with ELOG and threaded Msg's under Win 2k3 Server | Many Thank's to Stefan for his work!!! He's doing a great job and is offering a better
service than most comercial programs! Thank you very much Stefan!!!
The new elogd.exe is now runniung 24h on my Windows 2003 Server without any problems. I made
a little "stress" test too and there wasn't any problems at all. Also threaded view is
working stable now.
Is seems, that the new eleogd.exe uses a litle bit less of system rescources especially in
theraded view mode.
System specification for test: Pentium 4 2,4GHz, ASUS Motherboard, 480 MB RAM, SWAP File 1,1
GB, Windows Server 2003 Enterprise Edition 5.2 including all paches until 15.3.04, IIS 6.0,
Mercure Mail Server 4, McAffee Virus Scan & Firewall, ELOG 2.5.1 with new eleogd.exe runnig
as service (system righs) with FireDaemon Lite 1.6GE.
Please note that this problem has been occured under windows (reported for XP, 2000, 2003
Server) only. Windows NT 4.0 is working well without the new eleodg.exe as well.
> This problem has been fixed now, it was a programming bug. New version under
>
> http://midas.psi.ch/elog/download/windows/elogd.exe
|
|
68119
|
Mon Sep 21 17:08:44 2015 |
| Edmund Hertle | edmund.hertle@kit.edu | Question | Windows | 2.7.3 | Re: Syntax for conditional list display | Hey Terry,
I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )
Cheers
eddy
| Terry L wrote: |
|
Good Morning,
I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in. I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes. However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable. To expand on this, I may want to even limit the visibility of the attributes as well.
I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this? Is that section even relevant to what I want to accomplish?
Can anyone provide some guidance?
Thank you for your time & help!
Sincerely,
Terry
|
|
|
68134
|
Tue Sep 29 17:15:07 2015 |
| Terry L | trflin@yahoo.com | Question | Windows | 2.7.3 | Re: Syntax for conditional list display | Hi Eddy,
Thank you for your response. I had a feeling that was the case, but I had high hopes! :) The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee". If I am lucky, this will be an added feature in a future revision.
Thanks again,
-Terry
| Edmund Hertle wrote: |
|
Hey Terry,
I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )
Cheers
eddy
| Terry L wrote: |
|
Good Morning,
I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in. I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes. However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable. To expand on this, I may want to even limit the visibility of the attributes as well.
I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this? Is that section even relevant to what I want to accomplish?
Can anyone provide some guidance?
Thank you for your time & help!
Sincerely,
Terry
|
|
|
|
68135
|
Wed Sep 30 09:28:39 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.7.3 | Re: Syntax for conditional list display | Hi Terry,
if you really want to do it, you can find a way to make it work. But it is not straight forward and not what ELOG is made for. Here some ideas how it could work:
- ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
- You can use "
Subst on reply <attribute> = <string>" to set a specifc fields only on reply.
- You would hide "status" & "assignee" for new entries or edit
(Show Attributes Edit = <list>), and show a "set status" field instead.
- The line "
Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
- The list view or single entry view should not show the "set status", but only the "status" attribute (
List display = <list>, Show Attributes = <list>).
- Use "
Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.
This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.
Cheers, Andreas
| Terry L wrote: |
|
Hi Eddy,
Thank you for your response. I had a feeling that was the case, but I had high hopes! :) The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee". If I am lucky, this will be an added feature in a future revision.
Thanks again,
-Terry
| Edmund Hertle wrote: |
|
Hey Terry,
I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )
Cheers
eddy
| Terry L wrote: |
|
Good Morning,
I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in. I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes. However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable. To expand on this, I may want to even limit the visibility of the attributes as well.
I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this? Is that section even relevant to what I want to accomplish?
Can anyone provide some guidance?
Thank you for your time & help!
Sincerely,
Terry
|
|
|
|
|
68137
|
Thu Oct 1 12:01:11 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.7.3 | Re: Syntax for conditional list display | Oups: there is a flaw in this approach! You can only get different commands for Anonymous and Login Users. You cannot select different command for Admin users: they will just have the "Config" command automatically.
You could allow anonymous users to make new entries and restrict login to administrators. But that is certainly not what you want, so forget my suggestion altogether.
| Andreas Luedeke wrote: |
|
Hi Terry,
if you really want to do it, you can find a way to make it work. But it is not straight forward and not what ELOG is made for. Here some ideas how it could work:
- ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
- You can use "
Subst on reply <attribute> = <string>" to set a specifc fields only on reply.
- You would hide "status" & "assignee" for new entries or edit
(Show Attributes Edit = <list>), and show a "set status" field instead.
- The line "
Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
- The list view or single entry view should not show the "set status", but only the "status" attribute (
List display = <list>, Show Attributes = <list>).
- Use "
Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.
This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.
Cheers, Andreas
| Terry L wrote: |
|
Hi Eddy,
Thank you for your response. I had a feeling that was the case, but I had high hopes! :) The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee". If I am lucky, this will be an added feature in a future revision.
Thanks again,
-Terry
| Edmund Hertle wrote: |
|
Hey Terry,
I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )
Cheers
eddy
| Terry L wrote: |
|
Good Morning,
I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in. I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes. However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable. To expand on this, I may want to even limit the visibility of the attributes as well.
I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this? Is that section even relevant to what I want to accomplish?
Can anyone provide some guidance?
Thank you for your time & help!
Sincerely,
Terry
|
|
|
|
|
|
66890
|
Fri Sep 3 14:43:16 2010 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | Linux | Mac OSX | 2.8.0 | Re: Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined? |
| Glenn Horton-Smith wrote: |
|
We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it? [...]
I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized. This suggests it isn't specific to Linux architecture, 64-bit or otherwise.
|
We plan to use ELOG with mirror servers in a larger scale here, so I'm interested to know more about your problem.
Could you boil down your configuration to a minimum that still allows a reproduction of the problem and post those configurations as attachments?
Then I would try to reproduce it here. Best case I'll find a bug fix, worst case I'll reconsider the use of mirror servers ;-) |
|