Let me report when I see this behaviour.

If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,

but the running elog is still running with the old configuration.  You have to restart elog for it to read the new config file and

use the new settings.

This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg

just after it has been saved.

The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,

and it's quickest to cut-and-paste,  change the heading, create a new directory and restart elog.

This may be completely off what is being reported.

Hi Stefan,

Roptions, or Radio Buttons.  Do you recall that on old
radios, if you gently pressed a button you could release whichever
button was already in, without selecting the new button; in other
words no selection made.

I'd like this same facility with elog.  Now I know that it can be
done by (for example) in the config file preselecting one of the
selections on reply- or indeed one that does not exist to "clear" it, 
but in this case that is not the route I'd want to take every time.

What I'd like is a (optional) button along with all the others, which 
if you click on it, it will clear any selection for that particular Roption.  
At present, once an Roption has been selected, it will persist in all 
replies unless or until an alternative choice is made.  Alternatively, if 
no selection has been made, then there is no selection on the reply, either. 
[Unless something in the elog.cfg file].

Regards,

David.
 

> > I'd like this same facility with elog.  Now I know that it can be
> > done by (for example) in the config file preselecting one of the
> > selections on reply- or indeed one that does not exist to "clear" it, 
> > but in this case that is not the route I'd want to take every time.
> 
> What about defining an additional option "unspecified". So you have
> 
> Roptions attr = option1, option2, option3, none
> 
> Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does 
> not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want.

Hadn't realised the standard was written that way.  
What you propose seems fine to me.

David.

 I've a little experience of digging myself out of (in my case, self-induced) problems using ELOG.   I'm also aware that I may be the least experienced/qualified user..

First:  Archive your work directories.  Then at least whatever you do from here, you've got the status quo to fall back on.  Also, record anything you can remember (ID number, thread, etc) of the deleted entry/entries.

I've found that ELOG can hang in an infinite loop if it tries to find an entry that is no longer there - and that depends upon how you approach the point where the missing entry would be.  ELOG's own delete works fine in normal circumstances.  I'm talking about abnormal circumstances, for example when idiots (me) are playing around with the yymmdda.log files, or *possibly* if the disk is full, and you then try deleting the entry that caused the full disk problem.  Whether that is what you are seeing, I cannot say at present. 

However, to progress this:  When you are stuck, unable to edit anything, in a[nother] terminal, try the process report

ps -A

two or three times, with a short interval between commands.  (Or other switches if you know how to select to view the elogd process on your system).   If elogd is using seconds of CPU time between each ps command, it's probably in an infinite loop.  If you need to be sure, wait a minute and check again.  If so, you'll have to stop the daemon, possibly requiring a computer reboot.  In my experience, ELOG does not get stuck in an infinite loop when just indexing the pages when the daemon starts, but experts may well know better.

This may at least diagnose whether you cannot edit because ELOG is stuck in an infinite loop, or has some other cause.

If it is the infinite loop, the trick is to find which entry causes the loop without getting stuck in that loop next time around. 

David Pilgram.

Don't get too excited yet!

When you reply to an entry in ELOG, then some additional data is added to that original entry. 

So, if you reply today (say 02/06/11) to an entry made yesterday, then you will find that the file 110602a.log has a large change (the new entry in full, plus elog extra codes), *and* an additional line added into 110601a.log.  Deleting 110602a.log will not remove the line in 110601a.log, and that could still cause problems, that is, wandering into an infinite loop.

To save a lot of effort, I'll suggest that you (a) keep the back-ups up to date, and keep two (the latest and the one before that); (b) proceed carefully at least to start with.  If you fall into the infinite loop again, then flag it up and I (or someone else) will be able to give further pointers.

David Pilgram.

So unless you are sure that

Soren, you're not alone!  I've had similar problems, as did Sara Vanini (elog:67077).

In my case, it is because the "move" or "copy" function does not move all the messages in very long threads.   To be more precise, elog will crash in the attempt to move a long thread - say over 40 replies, I don't know for sure.  Sometimes it has already moved the entire thread before it crashes, sometimes not.  I'd not flagged it up as an issue because I could not be sure it was not a memory issue with the old (>12 years) linux box I was using earlier this year, but it still happens on this new (to me, only 3 years old) linux box.

Whether it is the number of entries, the total memory size of the thread or some combination, I don't know.

I've found that in the "move" case, it has not deleted all the messages from the donor thread, so that there is a semi-thread still hidden there.  Should one by chance select that semi-thread, (because it is found during a search) elog goes into infinate loop, which requires a reboot of this linux box to fix.   Certainly the pinning down the issue to the missing entry referenced by an <i>In reply to:</i> explains this part of the issue.  Of course, deletion of one entry within a thread, or other adjustments will do the same thing, just as you (Soren) point out above.

If it happens to me, I will go in to the yymmdda.log files and fix the problem, be it deleting the entries of the semi-thread, moving across missing entries from the donor to the acceptor logbooks, adjusting the <i>Reply:</i> and <i>In reply to:</i> lines, but that is quite a time consuming and error prone exercise.

Is it possible to have an attachment to an entry in a different directory to the working directory of the logbook being used?

By which I mean, if you have in logbook hidden the attachment files

../logbooks/hidden/110705_235520_whatthis-0.png
../logbooks/hidden/110705_235520_whatthis.pdf

that an entry in another logbook, public, can use the entries in hidden to show them (and do everything that you can do with an attachment)
without making another copy in public?

I see that if, working in public, you attach the .pdf file in hidden, the files get copied across as

../logbooks/public/110705_235520_whatthis-0.png
../logbooks/public/110705_235520_whatthis.pdf

that is, with the original (hidden) timestamp, and no second time stamp superimposed.  From which you can gather I've been playing around, manually editing a yymmdda.log file to try and get the result I want, even if for the moment it cannot be done via elog; but without success, although there were some bizarre interpretations by the elog program of the edited yymmdda.log file, depending upon what I tried.

For one entry, it is of course no big deal, copying the files into the public directory, but if you are dealing with multiple huge entries, it does seem wasteful of HD space

But my reason for this is that hidden has restricted access, whereas public has general access.  The attachments themselves are not restricted, but comments, history etc around them in the restricted access logbook should not become available to the general viewer.

OK, so no-one has ideas as per my question in elog:67088.

Looking at the issue from another angle.

If you attach a pdf file (for example), two files are added to the logbook:

../logbooks/hidden/110705_235520_whatthis-0.png
../logbooks/hidden/110705_235520_whatthis.pdf

Is there any way that you can select an attachent, but only the thumbnail (.png in this case) is stored (and
subsequently viewed)?  Options for ability to select an attachment, or how the thumbnail is manipulated/viewed
exist, but nothing about the storage or otherwise of the original document that I can find.

I've tried manually deleting the .pdf file (after going through the automatic routine to make an attachment),
and elog doesn't seem upset at the lack of the .pdf file at all.  The only time anything happens is if one
clicks on the image - and then you get a 'file not found' message from the browser - I could live with that.

In my case the original .pdf file is elsewhere, I've no need to have duplicates scatted in various logbooks, and
while ideally that would also be true of the thumbnail, it is fair enough for this to be stored in each logbook
where it is required.  This removes the issue of how to have an attachment in a different logbook (other than by
links, which would get rather tiresome to have to keep making).

Anyone any ideas?