Show last default = 0

always worked, even in my original code. It was just not documented. I added that.

Andreas Luedeke wrote:

Hi David, I was confused because one normally does not need to include a line in the configuration to set a default value. A default is exactly what you get if you don't specify anything in the configuration But I think I've figured it out: you were overriding the default in the global section for all logbooks and wanted to get back to the default for a particular logbook. Then another simple solution would have been to remove the line in the global section and add it just in those logbook configurations, where you actually need it. Anyway, it is good that one can now set the default in the configuration; I agree that this should always be possible. Cheers Andreas David Pilgram wrote: Hi Andreas, Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file.  In an archived logbook, it's perfectly possible for "all time" to be the only sensible value.  I tried "Show last default =  " and various other variants, with no success in getting what I actually required.  Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code. I've sent an email to Stefan giving my coding changes for information.

Hi Stefan,

here is a draft of how you could describe the webserver authentication in your docs.

T/Christof

> Stefan told me that the change was because some users were having thousands of yymmdda.log files
> in the logbook directories, and that sorting them into subdirectories by year at least did something to bring some 
> order.  Possibly to get around the lazy archivers, I suspect.

I'm actually the culprit, who did ask for it.

If you want to know the full story, here it is:
We have our logbook data of our accelerator operation logbooks on AFS (Andrew File System). 
And apparently AFS has a bloody stupid, hard coded limit: 
the total length of all file names in one directory cannot exceed 64k.
Our operation logbooks go back for more than a decade and do contain many, many, many attachment files.
One day - very unexpectedly - we did hit that limit. 
Removing temporary files (generated picture thumbnails) bought us time, and Stefan was nice enough to upgrade ELOG swiftly for us: a big "Thank You" to Stefan!

> > Stefan told me that the change was because some users were having thousands of yymmdda.log files
> > in the logbook directories, and that sorting them into subdirectories by year at least did something to
bring some 
> > order.  Possibly to get around the lazy archivers, I suspect.
> 
> I'm actually the culprit, who did ask for it.
> 
> If you want to know the full story, here it is:
> We have our logbook data of our accelerator operation logbooks on AFS (Andrew File System). 
> And apparently AFS has a bloody stupid, hard coded limit: 
> the total length of all file names in one directory cannot exceed 64k.
> Our operation logbooks go back for more than a decade and do contain many, many, many attachment files.
> One day - very unexpectedly - we did hit that limit. 
> Removing temporary files (generated picture thumbnails) bought us time, and Stefan was nice enough to upgrade
ELOG swiftly for us: a big "Thank You" to Stefan!


Hi Andreas,

I had no intention of causing any offence with my lazy archiving comment - hope I didn't, sorry if I did.  Just
that sometimes I've hit some limit or other, and
entirely due to my lazy archiving - I only get around to do it when I have to, usually when I've hit a limit, or
some other problem (broken links and orphaned
threads being common ones).   

Personally, I would have found it useful to put the attachments into a separate directory - or at least to allow
the possibility.  Elog as it stands sometimes
can, and sometimes cannot cope with that functionality - and even to try means messing around directly with the
yymmdda.log files.  For me it would have saved me
having duplicates of the same large attachment in two or three different logbooks, if I could always reference
the same Master copy of the attachment.  This was
at the time I was severely memory constrained, and in part forced me to change how I had operated elog, so for
me that need isn't as great as it once was.

David.

I had no intention of causing any offence with my lazy archiving comment - hope I didn't, sorry if I did.

Personally, I would have found it useful to put the attachments into a separate directory - or at least to allow

the possibility. Elog as it stands sometimes can, and sometimes cannot cope with that functionality - and even to try means messing around directly with the

yymmdda.log files. For me it would have saved me having duplicates of the same large attachment in two or three different logbooks, if I could always reference

the same Master copy of the attachment. This was at the time I was severely memory constrained, and in part forced me to change how I had operated elog, so for

me that need isn't as great as it once was.

David.

You can put a reference to the attachment of the other entry in your logbook: elog:67896/1

I am one who received an email every time there is a new entry in this forum.

I have just noticed that since May 20, every email contains the message "An old ELOG entry has been updated: "

whereas before that date, the vast majority say "A new ELOG entry has been submitted: "

Is this something to do with the saving of draft messages?

Talking of which, I see my draft of this message shows up in the forum before I have submitted it.

I acknowledge these two bugs and will fix them soon.