Hello

I have a config file  :

Attributes = Author, Author Email, Category, Customer, server,HPSD_ID, Cust_ID ,Subject ,  Change Window
; which fields will be shown !!
List display = ID,Author, Category, Customer, server, HPSD_ID, Cust_ID,Subject ,  Change Window

Type Change Window  = datetime
# Type Change Window End = datetime
Options Category = Network , Server ,
Options Customer = Arag{A}, Frieslandbank{B}, Super de Boer{C}, NRE{D}

{A} Options server = arag-lin1,arag-lin2,arag-lin3,arag-lin4, arag-lin5, arag-lin6, arag-lin7
{B} Options server = rc1upas02, rc1upas22,rc1upas03,rc1upas04,rc1uptsm01,rc1upas07,rc1upas08
{C} Options server = xia61031,xia61032 ,xia61033,xia61034,xia61035,xia61036,xia61037,xia61038,xia61039,xia61040,xia61032 ,xia61033,xia61034,xia61035,xia61036,xia61037,xia61038,xia61039,xia61040
{D} Options server = server27,server32,server34 ,server37,server38,server40
Extendable options = Category , Customer,server
Required Attributes = server , customer, Subject, Change window Begin , Change Window End
 

This works OK, However when I change the {A} Options  to {A} Moptions in the above code i get an error which tells me that a required field is not selected. So, with the pull down it works, with Moptions ( select boxes )  it will say that a required field is not selected.  Any hints ?

regards Arno

 I just found out that email notifications only worked for the first 50 users of this forum. So if you registered only recently, you might not have received any notification. This was a bug inside elogd which I hope to have fixed now (this entry notification will show...). If you get the first notification and do not want this, log in to the ELOG Forum, click on "Config" and remove the checkmarks from the logbooks you do not want to get notifications.

 Connect your PC to the internet and tell everybody the URL. Make sure the Windows Firewall allows remote access.

Please tell me how to share my elog with people.

> 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...

> I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old 
Debian
> 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.

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 ;-)

	reload)
		# Do nothing since ELOG daemon responds to 
		# the changes in conffile directly.
		;;

    reload)
        if [ -f $PIDFILE ]; then
            echo -n "$DESC to reread config file ... "
            kill -HUP `cat "$PIDFILE"`
            echo "done"
        else
            echo "No $PIDFILE found!"
        fi
        ;;

> > 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