config option?, posted by Andrey Pashnin on Wed Jan 4 11:03:45 2023
|
How about adding a config option?
Ideally, it might be nice to have this option "per record" or "per logbook", but "per instance" should be good enough. |
wrap "pre" tag in a "div" with fixed width, posted by Andrey Pashnin on Wed Jan 4 11:39:39 2023 
|
I'm sorry for being annoying...
but I have tried to wrap the <pre> tag in a <div> and it seems to do the trick
(the text is a single line with repeating aaa-b-cc sequence)
In the READ mode, the width is limited by the div's width
(see the first attachment)
In the EDIT mode, the width is only limited by the textarea width
(see the second attachment)
All this is with "wrap=hard" removed. |
|
config option?, posted by Andrey Pashnin on Wed Jan 4 11:53:35 2023
|
That's great! Thank you very much. |
|
RESOLVED HERE:, posted by Andrey Pashnin on Wed Jan 4 11:54:55 2023
|
see https://elog.psi.ch/elogs/Forum/69594 |
|
please DELETE this thread, posted by Andrey Pashnin on Wed Jan 4 11:58:19 2023
|
I added a reply to my previous post about this issue (a few months ago) to point to the solution, but ELOG moved it to the top of the forum.
And I cannot delete this now, because I change my user name from "Andrey" to "Andrey Pashnin" :)
"Only user Andrey can delete this entry" |
|
wrap "pre" tag in a "div" with fixed width, posted by Andrey Pashnin on Wed Jan 4 14:05:25 2023
|
Sorry, I forgot to mention that I also added some styles to the <pre> tag:
style="white-space: normal"
(see the screenshot on my previous post) |
|
white-space: pre-wrap", posted by Andrey Pashnin on Wed Jan 4 14:38:54 2023
|
> I guess we want "white-space: pre-wrap" which keeps the old line breaks.
Yep. You're right. Thanks! |
elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Peter Kovac on Mon Nov 27 17:29:41 2006
|
Greetings~
First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.
The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.
Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...
Thanks,
-Peter |