Re: Synchronising between physically separate networks, posted by Stefan Ritt on Thu Jul 10 12:46:52 2008
|
Dougie Mooney wrote: |
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:
- Stop the server on NET1
- copy logbook directories from NET1 to node2 of NET2
- start server on node2 of NET2 using the -M option
- once above complete, copy logbook directories from node 2 NET2 to NET1
- Start the server on NET1
Am I on the right track?
Would very much appreciate comments and and advice on the above.
|
A couple of comments:
- In principle you could use one elogd.cfg for two running daemons, but only if they do not modify the file. If you use "extensible attributes" for example, you would have write access. If this happens from both servers at the same time, the config file can get corrupt. This is even more true with a password file, which gets written every time a users accesses a page. If you only run one server at a time, then they can share the config file of course.
- The synchronization works bi-directional between two elog daemons. Requirement is that they have access to each other. The synchronization master acts like a "browser" to the slave to send/retrieve entries. So if you can affort punching a hole into your firewall between NET1 and NET2, you could synchronize two servers directly and don't have to bother with three servers. If you have however really physically separated nets, such that you need a memory stick to transport data from one net to the other, then indeed you need the above described scenario. I never tried it in this way, but in principle it should work.
|
Re: Supress Email to Author of a message?, posted by Stefan Ritt on Thu Jun 4 14:04:21 2009
|
Mike wrote: |
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?
|
Actually I do want to receive a copy, just to be sure that the emails got sent out correctly. I agree that an option would be good for that but it's not implemented right now. An alternative solution is to define a filter in their email client to discard these messages (like if subject contains ELOG and sender equals your own mail address). |
Re: Supress Email on Reply, posted by Stefan Ritt on Thu Sep 10 16:55:08 2009
|
mike cianci wrote: |
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"?
|
No, but you can remove the "Department" with
Remove on reply = Department
this way the attribute vanishes, but that should be ok since you always have the link to the original entry which contains the department. |
Re: Suppress Email notification checkbox, posted by Stefan Ritt on Thu Jul 7 22:02:52 2005
|
Gary Clayson wrote: | Hello All. Stefan, would it be possible to add one more option to the Suppress Default flag? I'd appreciate a setting that would suppress emails being sent and remove the option from the page. Or, has this been accomplished? And, if so, what is that setting. Thanks in advance!! Keep up the great work. |
I added
Suppress default = 3
which always suppresses email notifications. The addition is under CVS and will be included in the next release.
- Stefan |
Re: Suppress Email notification checkbox, posted by Gary Clayson on Fri Jul 8 22:20:19 2005
|
Stefan Ritt wrote: |
Gary Clayson wrote: | Hello All. Stefan, would it be possible to add one more option to the Suppress Default flag? I'd appreciate a setting that would suppress emails being sent and remove the option from the page. Or, has this been accomplished? And, if so, what is that setting. Thanks in advance!! Keep up the great work. |
I added
Suppress default = 3
which always suppresses email notifications. The addition is under CVS and will be included in the next release.
- Stefan |
Thanks Stefan. |
Re: Suppress Email notification checkbox, posted by Gary Clayson on Tue Jul 12 17:41:30 2005
|
Stefan Ritt wrote: |
Gary Clayson wrote: | Hello All. Stefan, would it be possible to add one more option to the Suppress Default flag? I'd appreciate a setting that would suppress emails being sent and remove the option from the page. Or, has this been accomplished? And, if so, what is that setting. Thanks in advance!! Keep up the great work. |
I added
Suppress default = 3
which always suppresses email notifications. The addition is under CVS and will be included in the next release.
- Stefan |
Hello Stefan. I used this setting with the beta2 version and it works great. THANX!!! Many kudos to you for an elegant solution to the logging 'problem'. |
Re: Support for modern Linux, posted by Stefan Ritt on Wed Nov 7 13:14:15 2012
|
Vinícius Ferrão wrote: |
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.
|
I'm not using Debian so I cannot give support there. There was some Debian support a few years ago, but the maintainer has gave this up. If you find someone who volunteers to do the job (yourself?) I'm happy to include the Debian specific files in the distribution.
Stefan |
Re: Support for modern Linux, posted by Graham Medlin on Wed Nov 7 13:45:10 2012
|
I'm not of the skill level to help, but for what its worth, running Ubuntu 12.04, used alien to install the latest RPM with only two little snags. I had to create a link from libssl.so.1.0.0 to libssl.so.6, which is a trick I've pulled with other software, not sure what the proper fix is. I also had to make similar changes to the init script. |