ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
195
|
Sat Jan 11 19:44:29 2003 |
| Etienne Van Caillie | etienne.vancaillie@mba.be | Request | | | call a shell from ELOG / new button [Submit & Notify] | propose to put
[Submit] [Back] [Submit & Notify] button on top/bottom
new parameter 'shell option'
[test]
...
Attributes = NotifyMode, Param1....Param10, Adresse, Subject, ...
Options NotifyMode = mail, SMS, Fax, printer...
; this command will invoque a shell command
; example
ShellCommand = <my shell command> parameters ...
like in WINDOWS 2000
ShellCommand = START.EXE notify.bat $NotifyMode $Param1, $Param2, $Param3
; in this case no necessity to modify the C source
; in windows I suggest the start.exe with a exit command
; so no necessary to wait the return code from the shell |
197
|
Mon Jan 13 11:45:18 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | | Re: call a shell from ELOG / new button [Submit & Notify] | I put this on the wish list.
- Stefan |
237
|
Tue Feb 25 22:35:44 2003 |
| Aamir Khan | aamir@aamir.uk.com | Request | | | elogd.cfg | Stefan and friends,
without breaching your own security, could it be possible to see what the
elogd.cfg file looks like, also if others would like to post theirs, this
would be great in building exmaples etc, obviosly an security related or
mail server entries hashed out.
I am a tad new at this stuff, but eventually would try my hand at getting
hold of the source code and compiling on AIX and then intergrating into
shell and error reporting. - OK .. a bit in the furture anyway, if someone
has already done this please post.
kind regards Aamir |
238
|
Wed Feb 26 10:13:10 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | | Re: elogd.cfg | > Stefan and friends,
>
> without breaching your own security, could it be possible to see what the
> elogd.cfg file looks like, also if others would like to post theirs, this
> would be great in building exmaples etc, obviosly an security related or
> mail server entries hashed out.
Ok, good idea. I made a new logbook "Config Examples" on this server, where
everybody can add new configuration examples. I added a few covering the
logbooks on this server as a starting point. Just click on "Config Examples"
at the top of this page! |
240
|
Thu Feb 27 10:53:09 2003 |
| Etienne Van Caillie | etienne.vancaillie@mba.be | Request | | | Re: elogd.cfg | > Stefan and friends,
>
> without breaching your own security, could it be possible to see what the
> elogd.cfg file looks like, also if others would like to post theirs, this
> would be great in building exmaples etc, obviosly an security related or
> mail server entries hashed out.
>
> I am a tad new at this stuff, but eventually would try my hand at getting
> hold of the source code and compiling on AIX and then intergrating into
> shell and error reporting. - OK .. a bit in the furture anyway, if someone
> has already done this please post.
>
> kind regards Aamir
we do recompile a version with ShellOnsubmit and ShellParam
and it works ! actually only on windows
when all test will be finish we'll send the version to Stefan Ritt
Attributes = By, Type, Categorie, Subject, Dossier, Remarks, email1
....
ShellOnSubmit = c:\test\shellTest\Debug\shellTest.exe
ShellParam = /Params %By %Type %Subject %Dossier %Remarks %
email1 /quietMode "test test"
|
309
|
Fri May 2 10:32:57 2003 |
| nickc1 | nick@nick.com | Request | | | Feature request - fairly urgent also :) | We are using elog as a small database system, today we came across a
problem where 2 people were editing the same record and the first one to
submit his changes were overwritten when the second person submitted his.
Is there anyway to lock a logbook record when someone has pressed EDIT,
maybe set a flag in the logbook entry so it has to be unlocked when its
submitted by the originator or by an administrator.
Many Thanks |
310
|
Fri May 2 10:39:51 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | | Re: Feature request - fairly urgent also :) | > We are using elog as a small database system, today we came across a
> problem where 2 people were editing the same record and the first one to
> submit his changes were overwritten when the second person submitted his.
>
> Is there anyway to lock a logbook record when someone has pressed EDIT,
> maybe set a flag in the logbook entry so it has to be unlocked when its
> submitted by the originator or by an administrator.
No, but I will put it on the wishlist. Anyhow it is hard to implement
something like this. Assume that I would lock a page whenever it's edited
by
someone. This person can edit it and forget to submit the changes, just
close
the browser. Since the elogd server does not know when a remote browser is
closed, it cannot determine if the editing is just taking long or if the
person closed the browser. In the latter case, the message would be locked
forever and nobody could change it any more. If I put a timeout, like keep
locked for N minutes, it's again not 100% safe. I saw people doing shift
work
with elog, opening a page, keeping it open for 8 hours and then submit it.
So
if I set the timeout to 8h, and someone abandons editing a message, this
message would be blocked for 8h, which is probably also not what you want.
Alternatively, I just can display a messge: Warning: this message is
currently edited by user xxx on host xxx. But if the warning is ignored by
the user, then again we have the same problem.
Do you see a clever solution to that? |
311
|
Fri May 2 11:05:28 2003 |
| nickc1 | nick@nick.com | Request | | | Re: Feature request - fairly urgent also :) | > No, but I will put it on the wishlist. Anyhow it is hard to implement
> something like this. Assume that I would lock a page whenever it's edited
by
> someone. This person can edit it and forget to submit the changes, just
close
> the browser. Since the elogd server does not know when a remote browser
is
> closed, it cannot determine if the editing is just taking long or if the
> person closed the browser. In the latter case, the message would be
locked
> forever and nobody could change it any more. If I put a timeout, like
keep
> locked for N minutes, it's again not 100% safe. I saw people doing shift
work
> with elog, opening a page, keeping it open for 8 hours and then submit
it.
So
> if I set the timeout to 8h, and someone abandons editing a message, this
> message would be blocked for 8h, which is probably also not what you
want.
>
> Alternatively, I just can display a messge: Warning: this message is
> currently edited by user xxx on host xxx. But if the warning is ignored
by
> the user, then again we have the same problem.
>
> Do you see a clever solution to that?
I was thinking of having an icon on the page that administrator can click
to
unlock a record that has been left locked by someone, perhaps using
something
like
Allow Unlock = admin (or even just have the option on the top like
(Admin/Config) for administrators
Just like the delete function works, in addition to the Warning message as
you suggested |
|