I would just like to present my opinion on this one... This change was introduced in Debian as fix for Debian bug 367105:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367105 Both configurations have valid use cases. I'm kind of in favor of having bacula file daemon listening only on localhost, as it is now. Why? Here is why... Bacula will never work out of box, cause of lots of configuration options that should be changed after installation. Changing listening IP address is just a tip of an iceberg. On the other hand, people that don't have any clue about bacula, and are just testing the software, are in danger. I would advise not changing default at least until we solve bug #222558 - each bacula client and daemon have the same password. This is cause password is generated on compile time. IMHO, talking about this and working on this issue should be post-intrepid. -- bacula client configuration is broken out of the box https://bugs.launchpad.net/bugs/286643 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
