Tomas send you by mail the source files and documentation in English



> > 1. shellonsubmit command : give the possibility to execute external 
> > program from elog by sending specific parameter (user/logbook/message ID)
> > 
> > 2. elog log file in xml format : give a better view on what happens with 
> > users see attachments easy to push the files to excel or sql database.
> 
> I'm happy to include these functions in the source code, please send them 
> to me.
> 
> > 3. synchronisation to mySql or SQL server through perl routine and the 
> > shellonsubmit command
> > this will push any new/edit/delete command in sql server so we keep a 
> > full historic off all transaction in ELOG
> 
> Can you please put this perl routine into the "Contributions" section
> 
> > 4. sms gateway : from elog entry we send sms message throught internet 
> > gateway (perl routine)
> 
> Same as above.
> 
> > other projet : 
> > we use a logbook from our external phone call
> > 
> > from our telephone connected to RS232 and/or TAPI interface we keep the 
> > phone number and try to find the name from sql server : if found 
> > we want to push an automatic entry in elog and fill specific field like 
> > name/contact/last phone call....
> > 
> > I will ask to Stephan Ritt what's the best way to include our routine in 
> > his standard source ?
> 
> As I said, put the perl programs into the "Contributions" logbook, send 
the 
> C source code modifications to me.
> 
> > could we create a specific logbook for the wishlist
> > in elog/contribution may be some parameters for the actual status of the 
> > project ? 
> 
> Good idea, will do so.

> > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> > 
> > 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> > to "echo ").
> 
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the 
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package 
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian 
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then 
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain. 

I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old Debian
one and working my way up till 2.7.5). Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
directory, with a suitable note in the README or something like that? That script has not changed in a long time and
is still functional - and doing so would make it easier for people who would like to install elog on a Debian (or
Debian-based, e.g. Ubuntu) system. I'll attach the script.

Regards,

Thomas

> The problem is not putting this into the "conrib" area, but supporting it. Since I don't have a Debian system, 
> may I suggest that you put it yourself into the elog:Contributions/ logbook. If people then get problems in the 
> future, they can contact you directly ;-)

I finally got round to do so. I've also included the changes suggested by Yoshio Imai (reload functionality).
Hopefully, it is useful for someone...

Hello Stefan,

I created a custom form with the example you provided. When I enter the Data and Submit the Form I get the error message "Datei passwordfile.xml kann nicht geöffnet werden: No such file or directory".  Posting stuff works in all other logbooks.  Only in the "logbook with the form" there seems to be an error. (or misconfiguration on my side)

sections from my conf. File:

I tried copying the password file to the forms directory, the logbook directory, the ShiftCheck logbook directory and the elog root folder.  I always get the same error.  I tried entering the absolute path, there was no difference in the result.

When I disable the password file I am able to post without any problems.  Can you help me out? 

Jonathan

There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:

Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S

Hi all! This is an HTTP POST request submitted from the command line using curl, and providing no authentication information. If I can post as myself using this command, then shouldn't something be done about this? Cheers, Dimitris