License conflict within syslogd/request for pidfile license change

I was looking at the sources to see what license
acknowledgements should appear when using syslogd.
While doing that, I discovered that syslogd.c is
BSD1 licensed (has the advertising materials clause), but is
linked with pidfile.c/pidfile.h, which is GPL licensed.
syslog.c is BSD2 licensed, so it isn't a problem.

Is there any chance of adding an exception to the pidfile.c/h
license to allow it to be linked with sysklogd.c with
advertising clause or dual licensing pidfile.c/h as BSD2 as
well as GPL? Otherwise, the syslogd process has conflicting
licenses which can only be resolved by writing a new pidfile.c/h.
Note that pidfile.c/h can't be licensed as BSD1, or it would
conflict with klogd components that are GPL.

Regards,
John Haller
Received on Mon May 11 2009 - 21:59:28 CEST