Stefan,
Thank you that is exactly what I needed to know.
Steve
| Stefan Ritt wrote: |
|
Deleting a logbook in the config page (via "Delete this logbook") only removes the logbook defiition from the config file. To really erase all information you have to go to the file system and delete the whole directory belonging to that logbook. You have one subdirectory per year, containing all logobok entries and also attachments, so make sure you do a recursiver directory removal.
Stefan
| steve bray wrote: |
|
Hello,
What is the procedure to delete a logbook (incl. attachments)?
Steve
|
|
|
Hello,
Has anyone implemented an email gateway for ELOG, allowing users to submit entries by sending an email? Granted this should be possible using the elog client binary, but I thought I'd see if I've overlooked any examples or docs first.
Thanks!
Devin |
I'm not sure I understand your question correctly.
If you want to remove options from an extendable option attribute, then you can just edit the logbook configuration file.
| John Mund wrote: |
|
Hello,
We have accumulated some duplicate 'types' in one of our logbooks. Is it possible to merge them?
Thanks,
John
|
|
Is it possible to submit entries using the elog client binary when the server is configured with webserver authentication (when the server requires the X-Forwarded-User header)? One option would be if the server could support both webserver and kerberos (or even file) authentication, but neither
"Authentication = Webserver, Kerberos" nor "Authentication = Webserver, File" seem to work.
In addition to using the elog binary to talk to the elog server directly, we've unsuccessfully tried using curl to post data to the apache server url (URL in elogd.cfg). We can read entries using curl, but haven't yet been able to submit entries.
Any help would be greatly appreciated.
Many thanks,
Devin |
We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.
But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.
If ELOG is down for two minutes a week, this is fine for our users.
| Stan Turner wrote: |
|
We have always had issues with eLOG crashing intermittently... I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues... which really didn't help.
The service now seems to crash every week... (getting worse)... Is anyone seeing these issues in Windows servers? Any suggestions??
|
|
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you |