SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Wed Nov 8 12:55:58 2006
|
| Stefan Ritt wrote: |
| Steve Jones wrote: | BUG: In the initial comment section of elogd_fancy.cfg the line # This [global] section contains settings common to all logbooks is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting with a comment char; |
Acknowledged. The problem was that the section between the line # This [global] section contains settings common to all logbooks and the real [global] section was interpreted as the global section, and thus the "real" one was omitted. I changed the code now such that all lines starting with a '#' or ';' are completely skipped, that fixes the problem. The fix is contained in revision 1745.
| Steve Jones wrote: | ISSUE: The option Logbook dir = causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?). |
That's weird. Have you tried to specify a full path for the logbook, like /nfs/some/directory ? The only difference of the daemon mode compared to the normal mode is that elogd does a cd to the root ('/'). If you specify logbook dir relative to the starting directory, like 'some/subdir', elogd will the try to access it under '/some/subdir', where it might not have read/write privileges. |
| Quote: | Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.
I'm putting this on hold for the time being as I now have test systems going into production. I'll be able to test next week.
|
|
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode, posted by Stefan Ritt on Wed Nov 8 13:07:31 2006
|
| Steve Jones wrote: | | Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately after that "cd /" test that things appeared to start not working - basically, elogd could not find anything. |
The "cd /" is mandatory for daemons according to Unix standards. If a daemon gets started on an NFS subtree, that subtree cannot be unmounted anymore. Therefor it's required that all daemons cd to root, such that the NFS subtree can freely be mounted and unmounted. I therefore use absolute paths in all my statements of elogd.cfg. |
Duplicate of a reply should be a reply, posted by Gerald Ebberink on Mon Jul 17 13:44:37 2006
|
Hello everybody
This weekend I found that if I duplicate a reply it does not become a reply it self.
Is this on purpouse?
I have been through the source a little (not much time for that) and I can not find a reason where the "in reply to" value is dropped.
Could anyone give me an pointer? |
|
Re: Duplicate of a reply should be a reply, posted by Stefan Ritt on Mon Jul 17 13:49:37 2006
|
| Gerald Ebberink wrote: | Hello everybody
This weekend I found that if I duplicate a reply it does not become a reply it self.
Is this on purpouse?
I have been through the source a little (not much time for that) and I can not find a reason where the "in reply to" value is dropped.
Could anyone give me an pointer? |
This is on purpuse. The Duplicate functionality is ment to "clone" an existing entry, to save some typing work if an existing entry contains most of what one wants in a new entry. If one duplicates a reply, it is detached from the original thread, so there is not entry to attach the duplicate to. I guess you want to make a new reply to an existing entry, and then have another existing reply as a template for that, but this is not possible. If I would not drop the "in reply to" value, the duplicate would point to the wrong entry. |
|
reply option in elog client not working, posted by Gerald Ebberink on Tue Aug 22 11:31:11 2006
|
When I try to make a reply with the following command
elog -v -h hostname -p 80 -l 'logbook wannabe' -u 'guess' 'what' -a 'Phase=During Measuring' -a Author='Gerald Ebberink' -a 'Subject=Octave measurements' -n 1 -f '22-Aug-2006 boxplot hole sizes of panel2SqTop.jpg' -f '22-Aug-2006 boxplot hole area of panel2SqTop.jpg' -f '22-Aug-2006 boxplot POA of panel2SqTop.jpg' -f '22-Aug-2006 boxplot hole sizes of panel2RTop.jpg' -f '22-Aug-2006 boxplot hole area of panel2RTop.jpg' -f '22-Aug-2006 boxplot POA of panel2RTop.jpg' -f '22-Aug-2006 boxplot hole sizes of panel6SqTop.jpg' -f '22-Aug-2006 boxplot hole area of panel6SqTop.jpg' -f '22-Aug-2006 boxplot POA of panel6SqTop.jpg' -f '22-Aug-2006 boxplot comparison of POA.jpg' -r 65 'Automated addition of measurment results (png)'
In verbose mode I found that the main difference is that
with the -r option it wants to go to the following url
Location: http://host/logbook/
and without it goes to
Location http://host/logbook+wannabe/66
my best guess would be that it should also point to logbook+wannabe |
|
Re: reply option in elog client not working, posted by Gerald Ebberink on Wed Sep 6 12:02:52 2006
|
| Today I found, I have the same problem with editing the log (with the -e option) |
Re: reply option in elog client not working, posted by Gerald Ebberink on Thu Sep 7 08:01:37 2006 
|
I have made patch witch solves the problem partialy.
If there are not no attachments this patch works.... (But since I have attachments I'll have to dig in deeper in the code.
Attached you will find the diff. |
astonished icon, posted by Elaine Cristina Franchini dos Anjos on Fri Jul 14 21:47:14 2006
|
Hi Stefan,
I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.
I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}
I copied the "astonished.png" to "eek.png" and it worked.
Is it the reason of the problem ? ?)
Thanks a lot.
Regards,
Elaine |