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. |
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? |
text display of ascii files not a good idea, posted by Heiko Scheit on Mon Aug 23 13:43:58 2004
|
I think the text display of ASCII files, which is new in version
2.5.4, is not a good idea. E.g. I had a large ps file attached
to one entry and it took a long time display this entry (over DSL).
Then I saw that the ps-file is displayed as text, which is not really
useful.
Probably it is fine to display only files ending in '.txt' per default.
In addition a file that has more than say 1000 lines should probably
also not be displayed (as default, optional OK).
Cheers, Heiko |
Re: elogd does not exit on SIGTERM, posted by Heiko Scheit on Fri Aug 27 00:49:27 2004
|
> 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. |
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. |
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). |
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). |