[kea-dev] [0.9.1-beta] Kea startup and logging

[Chaigneau, Nicolas]

Hello,


I have a few questions and comments about Kea startup and logging:



1)
I'm starting a kea-dhcp4 server configured with logging to a file.
Upon starting, the server outputs the following to console:

	2015-02-23 15:50:48.346 INFO  [kea-dhcp4.dhcp4/17854] DHCP4_STARTING Kea DHCPv4 server version 0.9.1-beta starting
	2015-02-23 15:50:48.348 INFO  [kea-dhcp4.dhcpsrv/17854] DHCPSRV_CFGMGR_USE_ADDRESS listening on address 10.163.216.230, on interface eth0.102
	2015-02-23 15:50:48.348 INFO  [kea-dhcp4.dhcpsrv/17854] DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type udp
	2015-02-23 15:50:48.348 INFO  [kea-dhcp4.dhcpsrv/17854] DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=60 name=/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv persist=true type=memfile universe=4
	(...)
	2015-02-23 15:50:48.351 INFO  [kea-dhcp4.dhcp4/17854] DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4 subnets: 1; DDNS: disabled


Nothing at all is written in the log file.
I suppose this is because the log facility must be initialized before anything can be written to the log file ?
In any case, it would be nice to have at least one line in the file such as:

	2015-02-23 15:50:48.346 INFO  [kea-dhcp4.dhcp4/17854] DHCP4_STARTED Kea DHCPv4 server version 0.9.1-beta started

So we can know from the log that the server has been really started and when exactly.



2)
When being started in non-debug mode, the process kea-dhcp4 does not daemonize itself (I have to terminate the command line with a '&').
Is that normal ?



3)
Each time kea-lfc is executed, we have:
- the following messages in Kea's log file:

	2015-02-23 16:18:53.891 INFO  [kea-dhcp4.dhcpsrv/17947] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
	2015-02-23 16:18:53.892 INFO  [kea-dhcp4.dhcpsrv/17947] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /opt/application/mwpdhcp/products/kea/0.9.1-beta-c2/sbin/kea-lfc -4 -x /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.2 -i /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.1 -o /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.output -f /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.completed -p /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.pid -c ignored-path

- but also the following on the console from which the kea-dhcp4 process was started:

	/opt/application/mwpdhcp/products/kea/0.9.1-beta-c2/sbin/kea-lfc -4 -x /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.2 -i /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.1 -o /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.output -f /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.completed -p /var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.pid -c ignored-path

I think the redundant console output should be removed.




Regards,
Nicolas.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.