I'm having problems with syslog-ng under both FreeBSD 5.2 and NetBSD 1.6.2 on the sparc64 architecture. For some reason, with my configuration, it thinks all log messages from remote hosts are actually coming from the current host. Even in chained hostname mode, all the messages came in with the hostname of the loghost itself. This seems to affect: FreeBSD 5.2 SPARC64 with libol 0.3.13 and syslog-ng 1.6.2 NetBSD 1.6.2 SPARC64 with libol 0.3.13 and syslog-ng 1.6.2 It seems to work perfectly fine with: FreeBSD 5.2 x86 with libol 0.3.12 and syslog-ng 1.6.1 OpenBSD 3.4 SPARC32 with libol ? and syslog-ng 1.5.24 While I went through many configurations, this is the last test case I used to demonstrate the issue: options { use_dns(yes);long_hostnames(off); chain_hostnames(on); owner(daemon); group(logreader); perm(0640); dir_perm(0750); dir_owner(daemon); dir_group(logreader); create_dirs(yes); }; source remote { tcp(); udp(); }; destination logremote { file("/var/log/ng/ALL.log"); }; log { source(remote); destination(logremote); }; Can anyone reflect a bit more on this? ----------------------------------------------------------- Thomas Stromberg <thomas@stromberg.org> Coordinator of UNIX Systems <tstrombe@indiana.edu> Department of Chemistry work://812-855-8450 Indiana University, Bloomington. cell://812-391-2843