Locking entries, posted by filantoro on Wed Sep 1 03:42:22 2004
|
I have a question about ELOG. Let's say after the user finishes his shift
and passess on to the next user on duty. A staff member would want to look
through the entries and vet them. The staff could lock the entries to
maintain integrity of the information. How can that be done with ELOG? Can
you enlighten me. Thank u. |
Re: Locking entries, posted by Stefan Ritt on Wed Sep 8 15:48:47 2004
|
One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.
Another way is to maintain two logbooks, a "scratch" logbook and an "archive"
logbook. Users would put their entries into the scratch logbook, the staff
would examine it and move them to the archive logbook, where all users only
have read access to. To move entries between logbooks, you have to put the
"Move to" command in the configuration file like:
Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help |
ELOG with stunnel won't show logbook, posted by Bartjan Wattel on Wed Aug 25 13:36:56 2004
|
Hi,
I have an ELOG installation on a RedHat linux server, called myserver. I
can connect to this server with the following entries in the elogd.cfg file:
[global]
URL=http://myserver:8080
This works fine. I can log in, select logbooks, edit/create entries etc.
etc.
However, I want this connection to be encrypted. So I activate stunnel (v4)
in such a way that stunnel listens to port 8081 and forwards to the
("remote") port 8080, which is the "original" elog port. I change the URL=
entry in de elogd.cfg file to URL=https://myserver:8081 in order to use the
SSL encrypted connection.
At this time, when I connect to https://myserver:8081 I get the
welcome/login screen, but when I enter the (correct) username and password,
the elog program does not show the contents of the logbook buts shows the
loginscreen again. If I enter a wrong username/password, I do get a correct
error-screen. So it seems that the connection is correct, but there is some
sort of problem in ELOG. Anyone who can give me a hand here? |
Re: ELOG with stunnel won't show logbook, posted by Stefan Ritt on Wed Sep 8 15:37:09 2004
|
That bug has been fixed recently, please update to the newest version. |
write access for elogd, posted by Dave Becker on Thu Aug 19 06:21:38 2004
|
Newly installed elog gives this response when I try to submit a new record:
New entry cannot be written to directory "./logbooks/Linux/"
Please check that it exists and elogd has write access
I started the daemon. I've not yet assigned passwords -- just checking
things out. How can I create this access to my own directory? |
Re: write access for elogd, posted by Stefan Ritt on Wed Sep 8 12:36:08 2004
|
> Newly installed elog gives this response when I try to submit a new record:
>
> New entry cannot be written to directory "./logbooks/Linux/"
> Please check that it exists and elogd has write access
>
> I started the daemon. I've not yet assigned passwords -- just checking
> things out. How can I create this access to my own directory?
First, find out under which account the daemon is running. It you account if
you start it interactively, if you installed from the RPM, an account "elog" is
created. Then make sure that the account under which elogd is running has write
access to the ./logbooks/Linux/ directory. One common problem is that people
start the daemon the first time under their account, which causes elogd to
create the logbook directory under the user name. If elogd is later started
under the account "elog" this one of course does not have access to the
directory. A
chown -R elog.elog /usr/local/elog/
issued as root could help in that case. Please replace /usr/local/elog with the
directory where elog is installed. |
Admin rights lost after upgrade 2.5.2 to 2.5.4, posted by nait tauh on Wed Aug 18 11:12:56 2004
|
The upgrade was done by just replacing elogd from 2.5.2 to 2.5.4 from the rpm.
Somehow elogd 2.5.4 treat all users as normal user. When clicking on
"config". All admin users has no "change elogd.cfg" button. Revert back to
2.5.2 OK.
Is there anything I need to change to upgrade other than replaceing elogd?
Clearing the cookies didn't help.
Thanks,
.nait. |
Re: Admin rights lost after upgrade 2.5.2 to 2.5.4, posted by Stefan Ritt on Wed Sep 8 12:25:20 2004
|
> Somehow elogd 2.5.4 treat all users as normal user. When clicking on
> "config". All admin users has no "change elogd.cfg" button. Revert back to
> 2.5.2 OK.
>
> Is there anything I need to change to upgrade other than replaceing elogd?
> Clearing the cookies didn't help.
The button name has been changed from "change elogd.cfg" to "change config file"
since the file name is now variable (can be changed during compile time). But I
guess this is not your problem.
Can you try with the demo logbook (contained in the distribution). Just add
"password file = ..." and "admin user = ..." to the sample elogd.cfg. If I do that
here, everything works fine. You also can send me your elogd.cfg so I can have a look. |
Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Wed Aug 11 18:02:22 2004
|
The help text on the website says the following:
"The command Select can be used to select multiple messages for deletion of
moving to other logbooks."
This is not clear but was the intent to indicate that SELECT can be used to
either select multiple log entries for deletion OR for moving to another
logbook? If the latter, then this does not work if one adds the MOVE TO
menu item to the list. If the former then the helptext is a little misleading.
Thanks! |
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Thu Aug 12 21:10:29 2004
|
> The help text on the website says the following:
>
> "The command Select can be used to select multiple messages for deletion of
> moving to other logbooks."
>
> This is not clear but was the intent to indicate that SELECT can be used to
> either select multiple log entries for deletion OR for moving to another
> logbook? If the latter, then this does not work if one adds the MOVE TO
> menu item to the list. If the former then the helptext is a little misleading.
SELECT can be used for deletion OR moving OR copying. To enable the copy and move
commands, they have to be present in the "Menu commands" list, like
Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Logout, Move to, Copy
to, Help
I added an appropriate note to the documentation, sorry for the misleading descriptoin. |
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Thu Aug 12 22:17:01 2004
|
> > The help text on the website says the following:
> >
> > "The command Select can be used to select multiple messages for deletion of
> > moving to other logbooks."
> >
> > This is not clear but was the intent to indicate that SELECT can be used to
> > either select multiple log entries for deletion OR for moving to another
> > logbook? If the latter, then this does not work if one adds the MOVE TO
> > menu item to the list. If the former then the helptext is a little misleading.
>
> SELECT can be used for deletion OR moving OR copying. To enable the copy and move
> commands, they have to be present in the "Menu commands" list, like
>
> Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Logout, Move to, Copy
> to, Help
>
> I added an appropriate note to the documentation, sorry for the misleading descriptoin.
Thank you. I had added the "Move To" and this works at the log entry level (i.e., "Move
To <name>) but in the threaded view one does not get the enumerated list of logbooks.
I'll play around with it a little more before re-posting. When it didn't work as I
expected I read the docs and ran across the confusing text - so I stopped and asked!
Thanks again. |
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Thu Aug 12 22:24:04 2004
|
> Thank you. I had added the "Move To" and this works at the log entry
level (i.e., "Move
> To <name>) but in the threaded view one does not get the enumerated list
of logbooks.
You get the "Move To" button only after pressing "Select", otherwise it does
not make sense. See attached screendump and config example. |
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Thu Aug 12 23:55:00 2004
|
> > Thank you. I had added the "Move To" and this works at the log entry
> level (i.e., "Move
> > To <name>) but in the threaded view one does not get the enumerated list
> of logbooks.
>
> You get the "Move To" button only after pressing "Select", otherwise it does
> not make sense. See attached screendump and config example.
Hmmm. I like the little buttons with the pull-downs for selections.
Unfortunately, I don't get that. With a config of:
Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help
my screen only shows the "toggle" and "delete" buttons. Was there a recent rev
that allowed this to happen (I didn't see a comment on this).
BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
to show multiple "Move To" links (one for each logbook) or should there also be
pulldowns?
Thanks |
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Wed Sep 8 11:44:56 2004
|
> Hmmm. I like the little buttons with the pull-downs for selections.
> Unfortunately, I don't get that. With a config of:
>
> Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
> Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help
Unfortunately menu commands are case sensitive, so you need a "Move to" instead a "Move
To". I changed this in the code so future versions will not be case sensitive any more.
> BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
> to show multiple "Move To" links (one for each logbook) or should there also be
> pulldowns?
On the log entry screen, only menu links are possible for internal reasons, that's why I
have chosen that display mode. I agree that it can look clumsy if you have many
logbooks, but there is the "move to = <logbook list>" option to restrict the number of
target logbooks. |
Options Items limits, posted by Patricio Castro on Tue Aug 31 20:29:20 2004
|
Hello friends,
Exist some form to increase limits of items (100) in the Options List
Thanks for any help |
Re: Options Items limits, posted by Steve Jones on Wed Sep 1 22:25:01 2004
|
> Hello friends,
>
> Exist some form to increase limits of items (100) in the Options List
>
>
>
> Thanks for any help
I believe only through an edit of the C code and a recompile, as the values
are set as constants. I think this might be the line:
#define MAX_N_LIST 100
So, yes, there exists a way and the ease of this way is dependent upon your
comfort level with changing stefan's code. |
Re: Options Items limits, posted by Stefan Ritt on Tue Sep 7 17:49:50 2004
|
> > Hello friends,
> >
> > Exist some form to increase limits of items (100) in the Options List
> >
> >
> >
> > Thanks for any help
>
> I believe only through an edit of the C code and a recompile, as the values
> are set as constants. I think this might be the line:
>
> #define MAX_N_LIST 100
>
> So, yes, there exists a way and the ease of this way is dependent upon your
> comfort level with changing stefan's code.
Agree. The only potential problem is that if this value becomes too big, you
will get a stack overflow from time to time. So best is experiment yourself a
bit. A avlue of 150 or so should be no problem.
- Stefan |
PostScript Files shown as text., posted by Bryan Moffit on Fri Sep 3 20:17:20 2004
|
At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog. Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).
Is there an option in the elog.cfg to only display certain files (like .gif
or .jpg). |
PostScipt Files shown as text., posted by Bryan Moffit on Fri Sep 3 20:17:12 2004
|
At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog. Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).
Is there an option in the elog.cfg to only display certain files (like .gif
or .jpg). |
|