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.

I'm also not familiar with Debian, all I know is that the former maintainer was Recai Oktas. See here for example:

elog:1002

Each time a attempt to CREATE A LOGBOOK on any of my logbook groups, I get an ELOG ERROR page presenting saying FORBIDDEN ATTRIBUTE DATE.

I have, up until recently been able to add new logbooks.

Can anybody help me on this.

Paraic Fahey

Just modify your configuration file elogd.cfg manually with an editor and add your logbooks there, then restart elogd.

/Stefan 

 I cannot answer for Windoze, BUT there is more to this if you use Linux.

(Sorry for re-entry, I spotted a cut-and-paste error from first time around)

If you want to make a new logbook in linux manually, you need to do the following:

0.  Stop the elogd daemon.

1.  Edit elogd.cfg as Stefan said.  This will be in two parts - at the top, and then a block of entries which is what you normally see when you go to the "config" section of any logbook.  Easiest to copy and paste an existing block, only remember to put in a new header in the square brackets at the top - the name of your new logbook.  While most of the elogd.cfg is the same as in the documentation, the additional headers etc are pretty self-explanatory, and you only see these because you're editing the file raw rather than through the elog interface.  Once restarted, you can then edit the config for the new logbook in the usual way.

2.  Create a new subdirectory in your logbooks directory *with the same name* as the name you added in when editing elogd.cfg.

3.  Give that subdirectory the correct ownership and permissions.

4.  Only then, start elogd again.

As a windows user, which of the above you need to do: create the subdirectory (I imagine so) and/or anything else (I don't know).  I don't use Windows - apart from AutoCAD and one other javascript based program that non-the-less has windows dependancies (!).

David.

 David, Stefan,

Thanks for your help. Directly editing the elog.cfd file worked.

Paraic

Stefan/Andreas,

When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."

The configuration file uses:

Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
 

The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.

As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.

But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.

Is this a bug -or- do I have to change the configuration?

Thanks & regards, Barend