Hello!

I was wondering if it is possible (and how) to define a template (something equivalent to an excel table with some required informations to be filled) that opens each time one wants to make a new entry of a given type, e.g., I want this template to open only when the informations concern data taking.

I hope I am sufficiently clear ...

Thank you,

I.M.

In ELOG you can define "attributes", so take one attribute for each informaiton you need. The flag these attributes as required via "Required attributes = ...". If you only want this attributes for certain occations (like data taking in your case), you can either do a separato logbook for data taking, or use "conditional attributes" to make these attributes only show up for data taking.

/Stefan 

When there are attachments in an entry, logbook is adding additional "MIME-Version" header to e-mail messages.

Spam filter in our university system is mostly giving warnings:

• X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"

But sometimes it is not redirecting further the message.

• Remote Server returned '< #5.6.0 smtp; 554 5.6.0 Bounce, id=27666-07 - BAD HEADER>'

In code I noticed there is always "MIME-Version" header added to the message and additionaly it is added again when a file is attached. I think it is not neccessary to add again this header.

I just checked the current installatin, and just found one MIME-Version in the header, even with attachments:

MIME-Version: 1.0
--------------717E3059287C82F12BC14941
Content-Type: multipart/related;
  boundary="------------4543EB0E5AAC14B461D70512"

No idea where your second header comes from, but sometimes I have seen some SPAM filters adding things to headers.

Stefan

Is there a way to post a logbook entry to a future dated logbook file?  I've searched through the user manual for forward dating but can't seem to find anything.  As an example at my office, a user wants to add a personal entry stating they will be absent from work on October 5th and I would like that entry information written to the 131005a.log file instead of the current days log.

I know two ways to do this. Either way you do need some kind of sysadmin status.

Stefan, Andreas, close your eyes for the next sentence.

1.  Set the computer/server clock to 5th October, make the entry, set the clock back again.

2.  Make the entry as normal, then go into the logbook directory and find today's 130912a.log entry - now create a new 131005a.log file, and paste in the relivant entry into this - not forgetting to change the day and date at the top.  Save the file.  Ensure that 131005a.log has the correct permissions and ownership (compare with all the other files) - you do mean you're using linux, didn't you.  Cannot answer for what to do/happen with Windows.

Now I too have this issue - there is one entry I want to keep at the very top of the list until a certain date has passed.  The way that Stefan/Andreas may offer probably will work, but I've never tried it - which is that the entry goes into today's log file, but has a "entry date" category.  I don't know if that would keep the entry at the top of the list until the 5th October has passed.  As I don't want to have an "Entry date" category, I resort to one of the two methods above.

The fact that the ID numbers become out of sequence doesn't seem to affect the performance of ELOG at all in my perhaps rather more extensive experience than the developers would have wanted me to try.

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

 I have asked for same help, and no one has answered with a solution on implementing a kerberos .  I saw exactly what you were seeing. (did you try fully qualifying the domain within the username field for logon?  \\TEST.COM\username)

I still couldn't get it to work