Giter Site home page Giter Site logo

sys-syslog's Introduction

NAME

Sys::Syslog - Perl interface to the UNIX syslog(3) calls

DESCRIPTION

Sys::Syslog is an interface to the UNIX syslog(3) program. Call syslog() with a string priority and a list of printf() args just like syslog(3).

INSTALLATION

To install this module, run the following commands:

$ perl Makefile.PL
$ make
$ make test
$ make install

An ANSI-compliant compiler is required to compile the extension.

Sys::Syslog should work on any Perl since 5.6.0. This module is regularly compiled and tested by the CPAN Testers on various combinations of Perl and operating systems.

See also the corresponding CPAN Testers page: http://testers.cpan.org/show/Sys-Syslog.html

SUPPORT AND DOCUMENTATION

After installing, you can find documentation for this module with the perldoc command.

perldoc Sys::Syslog

You can also look for information at:

COPYRIGHT AND LICENCE

Copyright (C) 1990-2012 by Larry Wall and others.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

sys-syslog's People

Contributors

chorny avatar dsteinbrunner avatar jkeenan avatar maddingue avatar tonycoz avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

sys-syslog's Issues

nofatal does not work (as advertised)

The "nofatal" option to openlog() does not work as suggested in the man page for this module. Calling program always exits out.

I was able to "fix" this by correcting what I think is an error in the code: $err_sub is supposed to be a coderef, if the comments in the code are to be believed. What I did is:

my $err_sub = sub { $options{nofatal} ? &warnings::warnif : &croak; };

I'm not sure why there are two places where this "coderef" is set, since the reference assignment in openlog should be sufficient given the man page says that openlog should always be called first. I also don't understand why the reference assignment in openlog insists on using "delete," but perhaps there is good reason to do this.

With my changes, the module seems to work with the nofatal option set, and it does not cause the calling program to crash or exit. The only problem is some annoying warnings about use of uninitialized value $current_proto in string eq.

CPAN Pull Request Challenge - February 2015

Hey Sébastien,

This month I got Sys::Syslog as my CPAN Pull Request Challenge. You can read more about it here: http://blogs.perl.org/users/neilb/2014/12/take-the-2015-cpan-pull-request-challenge.html

I've taken a look at Sys::Syslog on rt.cpan.org and seen there are a number of open issues, but I think some of them can be closed as-is and others I'm not sure how to help on.


Github? - Can be closed, Sys::Syslog is clearly on github already ;-)

trailing new line with perror - This one has a patch, but no test. I tried writing a test for it but couldn't reproduce the problem the original poster is referring to.

Handle getprotobyn{ame,umber} not being available - Lots of discussion. Some patches. Maybe already applied?

Syslog Bug? - FreeBSD 9.2, Perl 5.16, messages coming through at the wrong level.

closelog(): wrong handling of syslog flags - "quite serious bug in closelog()"

Conditionalize the use of setlocale/LC_TIME - closely related to Handle getprotobyn{ame,umber} not being available

Use fallback/syslog.h if I_SYSLOG is not defined - Applied already, so I think this ticket should be closed.

[regression] facility from openlog() is not used - Applied already, ticket should be closed.

Description for Event ID 157 cannot be found on Windows 7 - Windows bug, and it seems none of us have access to a windows machine!

Invalid usage of function POSIX::_exit - Fix applied, ticket should be closed.

Typo in POD - Typo fixed, ticket should be closed.

test t/facilities-routing.t fails - Fix applied, ticket should be closed.

escape escapes - Lots of good discussion here. Looks like the discussion moved from rt to P5P in 2009... did this get solved?

escape codes - Last comment from 2008 says "I can't tell whether it just works or if nobody realised there is a problem." Still true?

Use of encoding - Looks like nothing happened here?

Code works with Solaris 8, but not with Solaris 10 - I think this got solved in 2008?


If there's anything I can do to help let me know :-)

I'm going to send you at least one small innocent pull request this evening to fulfil the CPAN PR Challenge requirements, but I'd much rather make a meaningful contribution.

Thanks,

Alex

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.