behringer24 / yaul Goto Github PK

Add internal metrics to control behavior. Not sure how to output the collected data and when. As UDP reply on command, to syslog or a dedicated logfile or default logfile yaul.log?

Add the ability to use '/' in the logname to build namespacing that expands into subdirectories

Allow long options for command line configuration as described here:
http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html

To allow proper logrotting and sending HUP signal to daemon the actual pid must be written to /var/log/yaul.pid and kill -s HUP must be sent to the daemon after logrotation to close and reopen all opened files. Not really a bug but essential for proper usage.

Read Configuration from yaul.conf to reduce number of command line options.

Not sure if it is better to remove command line options or both ways should be provided.

Allow namespacing via dots in logname. The filenames will be generated accordingly.

Use faster data structure as handle buffer instead of simple linear array searching.

Add option to allow output buffering for logfiles. The Option sets the number of messages before the output buffer is flushed. Best would be the option -b for buffer - this would make it necessary to change the bind option which takes the ip adress to -i for IP adress.

Configuration by file of where the logmessages should go depending on the logname. Possible Destinations are

• other logname
• Redis
• Redis other logname
• UDP IP and port
• UDP IP/port and other logname
• null (discard)