https://bugzilla.balabit.com/show_bug.cgi?id=107 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu --- Comment #1 from Gergely Nagy <algernon@balabit.hu> 2011-01-06 19:26:05 --- I tried a postgres destination without explicitly specifying the port, and it just worked. On localhost, it just worked, when I specified a remote host (which had no postgres listening), it figured out the correct port, and tried to connect there. I'd assume the problem lies within libdbi, as when no port is specified, syslog-ng sets the port option on the DBI object to 0. My version of DBI (Debian Squeeze) treats the zero port as "use the default" (verified, just had a look at the libdbi-drivers source). Judging by the libdbi-drivers CVS tree, every other version of libdbi should behave in a similar manner. Why it still tries to connect to port 0 though, is beyond me, but the ball's in libdbi's court, in my opinion. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.