Hi,
that Sebastian would be me. I replied to the first entry, as it was a draft (site reloaded incorretly...) and now I can't see the post anywhere. But this is off topic.

We have elog running on port 8000 and forward the traffic via Apache to it. Apache handles the SSL and other sites on the server.
All you need is a apache site configuration like the following. The parameter you want is CustomLog. (Have a look in the internet for options.)
I have also used nginx as webserver and know it can also handle this proxy setup.
If you use the following config, the elog config needs the URL attribute in the (global) config.

Best wishes,
Sebastian

<VirtualHost *:443> # change 443 to  80, if you don't use SSL
        ServerName your.server.name

        # delete the next 3 lines, if you don't use SSL
        SSLEngine on
        SSLCertificateFile /path/to/your/ssl.crt
        SSLCertificateKeyFile /path/to/your/ssl.key

        ProxyPreserveHost On
        ProxyPass / http://127.0.0.1:8000/
        ProxyPassReverse / http://127.0.0.1:8000/

        # Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/access.log combined
        ErrorLog ${APACHE_LOG_DIR}/error.log

</VirtualHost>

Thank you soo much Sebastian once again for helping me!! This is something that will help me very much in the future with other situations similiar!

John :)

See https://elog.psi.ch/elog/config.html#mirroring

and

https://elog.psi.ch/elog/userguide.html#access

(use "find" with "Export to" "Raw".)

> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Yepp, this is a (missing) feature of the elog command. Can you pre-process your messages outside of it, or do I have to add code to elog to do that?

Stefan

Well I answered part of my own question already.. I can have a start page different from what is default, and I can edit the orginal one by simply copying it and modifiying it to my hearts desire. I still have isues  after making menu selections from that page tho,  when the program (server) takes me to a site called  for example: ../forum/index.html?cmd=Config. I cannot find out how to prevent or modify this behaviour. I am supposing tho, that because I am using my own original index.html (start page), that the program is not modifying it (on the fly), like it does with the oringal web pages?  I am also still currious if the program does indeed create/modify pages on the fly, and if it does, where does it store them on my hard drive (or is it only put in memory temporaly?). Thanx again :)

Per default, all pages are created dynamically by elogd directly from its C code. So nothing to change easily except hacking the code. There is one exception which is the start page you found already. To change any other page, you have to modify the C code. There is one more (dirty) trick: You can sneak in JavaScript code on every page via the "bottom text" option. This code can then modify the DOM tree and changes pages, but you need to program this in JavaScript.

Stefan