Front page | perl.perl5.porters |
Postings from April 2007
On 4/29/07, Randal L. Schwartz <merlyn@stonehenge.com> wrote: > >>>>> "Ævar" == Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes: > > Ævar> On 4/29/07, Randal L. Schwartz <merlyn@stonehenge.com> wrote: > >> > >> ext/Sys/Syslog/t/syslog.........................# Failed test 'syslog() > >> should return true: '0'' > >> # at ../ext/Sys/Syslog/t/syslog.t line 152. > >> > >> is this known, or does someone want me to run something more for tests? > > Ævar> Run it with verbose and show the "connecting to a" .. message two > Ævar> lines above that one. Seems like syslog via socket doesn't work on > Ævar> your system. > > > ok 1 - use Sys::Syslog; > ok 2 - Sys::Syslog->can(...) > ok 3 - calling setlogsock() with no argument > ok 4 - calling syslog() with no argument > ok 5 - calling syslog() with one undef argument > ok 6 - calling syslog() with one empty argument > ok 7 - setlogsock() called with 'unix' > not ok 8 - setlogsock() should return true: '0' # TODO minor bug > > # Failed (TODO) test 'setlogsock() should return true: '0'' > # at ext/Sys/Syslog/t/syslog.t line 82. > > I have nothing odd on my system. Perhaps syslog doesn't listen > on a socket on OSX. > > Hmm. lsof shows that it does: > > syslogd 81 root 16u IPv4 0x5852e10 0t0 UDP *:50982 > > Anything else you want me to try? That's a failure on line 82 not 152. Can you paste the whole output with all failures? I don't maintain Sys::Syslog though and I'm not really familiar with it so this is as far as I go:)Thread Previous | Thread Next