Hi there. Just started recently set up the application and think its very usable and easily configured - great stuff

I'm looking to roll it out to the masses but have a slight logistical problem in that we work on 2 separate networks - NET1 with connection to the internet, and NET2 physically isolated from NET1 and the internet.

It would be desirable to allow users to add/update/delete logs from both NET1 and NET2 with periodic synchronisation.

I believe the mirroring facility is what should be used, and think the following setup and synchronisation steps may be workable:

Setup:

• elog installed on node of NET1
• elog installed on 2 nodes of NET2
• elog server running on NET1 and node1 of NET2 both using a common elogd.cfg

Performing Synchronisation:

1. Stop the server on NET1
2. copy logbook directories from NET1 to node2 of NET2
3. start server on node2 of NET2 using the -M option
4. once above complete, copy logbook directories from node 2 NET2 to NET1
5. Start the server on NET1

Am I on the right track?

Would very much appreciate your comments and advice on the above.

Cheers Dougie

I couldn't find an obvious solution to the problem. I'd like to suppress email

notification to the author of a message. I've had some people complaining

that when they use elog they don't want to get an email about what they wrote

since they wrote it.

Is it possible?

Regards,

Mike

The way I have ELOG configured it sends an email to supervisors based on which "Department " (attribute) was selected. Problem is that when the supervisor replies the department

is still selected and it sends a second email to the supervisor. Is there any way to supress the emails (automatically) on "Reply"?

Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

The second problem is in this line:

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.

After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...

And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?

Many thanks in advance,

Vinícius Ferrão 

PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.

Hello,

when using the summary view, the text field displays umlauts as HTML-charachters, for e. g. diesbezüglich. 
Is there a chance that also this view displays umlauts as ä, ü, ö?

Thank you!

Uwe

It is possible to show the (new) text of a replied entry in the summary text field ?

Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.