Bug#360530: bacula-common: tcpwrapper config not documented

2006-06-29 Thread Kern Sibbald
Hello, Yes, the tcpwrappers name that the daemons look for in libwrap is not the daemon name. This is because there can be multiple simultaneous Bacula daemons running on the same machine. They simply use different .conf files. The fact that you must use the daemon Name as defined in the .con

Bug#360530: bacula-common: tcpwrapper config not documented

2006-04-02 Thread Greg Vickers
Package: bacula-common Version: 1.36.2-2sarge1 Severity: important Hi, tcpwrappers looks for the service name of the bacula daemons in hosts.allow, and the service names of these daemons is configured to be different from the binary! The service names are configured to be %hostname%-%component% r