Great! Thanks a lot for your patch. I appreciate if people not only come up with problems, but have already the solution. I committed your patch to the distribution, so it will be included in the next version.

- Stefan

If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Note the attachment to this post.

----

Makefile has the line:

# flag for SSL support
USE_SSL    = 1

However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
 You have to comment them out.

Lines 76-85 of Makefile should be replaced with this:

ifdef USE_SSL
ifneq ($(USE_SSL), 0)
CFLAGS += -DHAVE_SSL
LIBS += -lssl
endif
endif

ifdef USE_CRYPT
ifneq ($(USE_CRYPT), 0)
CFLAGS += -DHAVE_CRYPT
LIBS += -lcrypt
endif
endif

Thanks,
amartin

> If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
> the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
you, I would like to keep it as it is.

> Makefile has the line:
> 
> # flag for SSL support
> USE_SSL    = 1
> 
> However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
>  You have to comment them out.
> 
> Lines 76-85 of Makefile should be replaced with this:
> 
> ifdef USE_SSL
> ifneq ($(USE_SSL), 0)
> CFLAGS += -DHAVE_SSL
> LIBS += -lssl
> endif
> endif
> 
> ifdef USE_CRYPT
> ifneq ($(USE_CRYPT), 0)
> CFLAGS += -DHAVE_CRYPT
> LIBS += -lcrypt
> endif
> endif

The original idea was that one outcomments the whole line, like

#USE_SSL = 1

which always worked, but I agree that your solution is more general, so I changed the official Makefile. Thanks for 
that.

> > If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
> > the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
> 
> Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
> For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
> followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
> 0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
> easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
> find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
> you, I would like to keep it as it is.
> 

Thank you for your response.  

I can certainly use another filename, but I'm curious why elog doesn't convert the filename "000000_000000_file.txt" to
"YYMMDD_HHMMSS_000000_000000_file.txt" when it gets uploaded.  All other files are automatically prepended with this
string.  Manually renaming the file and then editing the elog entry via text editor seems to fix the file.

thanks,
amartin

all instances of elogd use the same file name in /tmp when calling my_shell.  This can cause some inconsistent behavior when two or more copies of elogd are runnnig at the same time.  (eg. one might detect ImageMagik is installed, and the other not,)

The propsed solution is to have the parent read from a pipe to the child rather from a file.  A patch is attached.

this elog gives errors sending mail through PSI email server. (did not capture the error messages, sorry). K.O.

this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
methinks I should only be offered to edit draft messages that I own or I can edit. K.O.

> this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
I find it odd that I can see someone elses draft, but never one that I am in the middle of composing (using a
different tab of the browser) in the elog listing.  There's one such draft Konstantin refers to in the logbook
listings now - last one was dark blue, this one a pink background, is there a reason for these different colours?