{"id":32210318,"url":"https://github.com/robohack/newsyslog","last_synced_at":"2026-02-20T16:02:10.189Z","repository":{"id":75162661,"uuid":"240618182","full_name":"robohack/newsyslog","owner":"robohack","description":"An enhanced and more portable version of `newsyslog` -- a tool for archiving log files","archived":false,"fork":false,"pushed_at":"2025-04-14T00:45:08.000Z","size":417,"stargazers_count":5,"open_issues_count":1,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-10-22T06:38:08.072Z","etag":null,"topics":["archiver","cron","logfiles","logging"],"latest_commit_sha":null,"homepage":"http://www.planix.com/~woods/projects/newsyslog.html","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/robohack.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2020-02-14T23:48:27.000Z","updated_at":"2025-04-14T00:45:12.000Z","dependencies_parsed_at":"2025-04-14T01:26:45.151Z","dependency_job_id":"e92d76cf-5a6e-4e0e-9f41-19d3d1a4384a","html_url":"https://github.com/robohack/newsyslog","commit_stats":null,"previous_names":[],"tags_count":27,"template":false,"template_full_name":null,"purl":"pkg:github/robohack/newsyslog","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robohack%2Fnewsyslog","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robohack%2Fnewsyslog/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robohack%2Fnewsyslog/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robohack%2Fnewsyslog/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/robohack","download_url":"https://codeload.github.com/robohack/newsyslog/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robohack%2Fnewsyslog/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29656589,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-20T09:27:29.698Z","status":"ssl_error","status_checked_at":"2026-02-20T09:26:12.373Z","response_time":59,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["archiver","cron","logfiles","logging"],"created_at":"2025-10-22T06:30:35.534Z","updated_at":"2026-02-20T16:02:10.184Z","avatar_url":"https://github.com/robohack.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"NEWSYSLOG -- A portable and enhanced version of this old standard\n\nThis file:  Copyright (C) by Planix, Inc.\n\t    see COPYING for details\n\nThis is an updated version of a package put together by Theodore Ts'o ,\nof MIT Project Athena (which is included in NetBSD, FreeBSD, OpenBSD,\nand probably other OS' too).\n\nWhat does this version of newsyslog have to offer over others?\n\n\t- It is more portable (using GNU Autoconf) and it can be\n\t  compiled and installed on most any modern Unix or Unix-like\n\t  system.\n\n\t- It has support for fixed time-of-day daily archiving with a\n\t  command-line option to identify the daily roll-over invocation\n\t  (which may be at midnight, or at any other regular daily time).\n\n\t- It supports the FreeBSD feature that allows specification of\n\t  the log roll-over time as a daily, weekly, or monthly interval\n\t  (with optional time-of-day specification for the last two).\n\t  [The other overly flexible, ISO 8601 interpretation of the\n\t  interval \"@\" option is not supported -- it is too generic and\n\t  not meaningful enough in the context of log file management.]\n\n\t- It supports optional PID files so that non-standard daemons\n\t  can be told to re-open their logfiles after archiving has\n\t  taken place.  (Including /dev/null which disables signalling\n\t  of any daemon when the specified log file is rolled over.)\n\n\t- It can send a signal other than SIGHUP to the daemon\n\t  associated with a given log file.\n\n\t- It can leave the most recently archived log file uncompressed,\n\t  which is necessary for daemons like httpd and smail because\n\t  they continue to write to the current log file until their\n\t  current jobs have completed.  (This also makes it much easier\n\t  to review recent log data with normal Unix tools.)  [NetBSD\n\t  now has this feature.]\n\n\t- It supports the FreeBSD feature of being able to restrict\n\t  processing to just those log files specified on the command\n\t  line.\n\n\t- Unlike the NetBSD version it first parses the config file\n\t  before taking any action, meaning that if any errors are\n\t  encountered it will report them and quit without doing\n\t  anything.\n\n\t- Unlike the FreeBSD version, it will roll a log file if\n\t  *either* the interval or size limits have been reached\n\t  (FreeBSD's version makes it too easy to have a rapidly growing\n\t  log file overflow the filesystem).\n\n\t- Unlike the NetBSD version it always creates any missing log\n\t  file (though this can be disabled on a per-file basis).\n\n\t- It uses an advisory lock on the current configuration file to\n\t  prevent multiple invocations from tripping over each other.\n\n\t- The documentation is far better!\n\n(For more specific details and recent changes see the NEWS file.)\n\n\nTO BUILD NEWSYSLOG\n\nNormally you should just follow the instructions in the INSTALL file\nunless special instructions below apply.\n\n\nTO BUILD NEWSYSLOG on *BSD SYSTEMS\n\nIf you are building newsyslog on a BSD-based system you can also use\n\"Makfile.BSD\".  This is in fact necessary if your system requires\ninstallation of pre-formatted manual pages (otherwise you'll have to\ninstall them by hand).  The simplest way to do this is to run the\n\"newsyslog2netbsd.sh\" script, then go into the \"import.d\" directory\ncreated by the script, check the Makefile and possibly update the\ndefault options in it, and finaly then simply run \"make\".  Note that if\nyou want to change the location of the install, or other pathnames then\nyou should change them in the \"newsyslog2netbsd.sh\" script *before* you\nrun it:\n\n\t# inspect and/or edit newsyslog2netbsd.sh\n\tsh newsyslog2netbsd.sh\n\tcd import.d\n\t# inspect and/or edit Makefile\n\tmake\n\tmake install\n\nThe same procedure should work fine for FreeBSD if you add\n\"__FreeBSD__=1\" to the make commands above.  OpenBSD may masquerade well\nenough as NetBSD, w.r.t. how makefiles work anyway, for OpenBSD users to\npretend while running make that they are using NetBSD.  :-)\n\nIf you actually do copy the contents of the import.d directory into your\nsystem source tree to replace your native newsyslog then you should add\nthe appropriate __*BSD__ definition to the Makefile.\n\nOf course newsyslog can also be built using the GNU Autoconf based build\nsystem and a ``normal'' (i.e. Unix compatible) \"make\".\n\nPlease see the file \"INSTALL\" for overall instructions on how to\nconfigure and build this package using the GNU Autoconf generated\n\"configure\" script.\n\nIn general you need only run the following command sequence:\n\n\t./configure \u0026\u0026 make \u0026\u0026 make install\n\n(see \"CUSTOM CONFIGURATION OPTIONS\" below for other \"configure\" options)\n\n\nBUILDING ON SYSTEMS WITHOUT TROFF \"doc\" MACROS (including Solaris)\n\nOn systems without the \"doc\" macros (or without \"nroff\", or even with\njust an incompatible version of \"soelim\"), you can still install and\nread the distributed 'cat'-table manual pages.\n\nFor example if you get an error during the first \"make\" that says\nsomething like \"nroff: Cannot find library -mdoc\", or \"nroff: not\nfound\", or \"-I: No such file or directory\", then run the following\ncommand instead of running \"make install\":\n\n\tmake copy-dist-mans install\n\nThis does not guarantee your \"man\" command will be able to find and\npresent the resulting files, of course.  If you really get into a bind\nover this the best I can suggest is to write a small \"wrapper\" manual\npage using the old-style man(7) macros that directs readers to view the\npre-formatted file in whatever location it gets installed in.  On some\nsystems you might be able to fool the \"man\" command into displaying the\npre-formatted version if you supply a dummy nroff source file that has\nan older timestamp than the pre-formatted file.  Fooling \"catman\" to get\na proper index entry for \"apropos\" (\"man -k\") might be harder, but on\nmost systems the index file is just plain text (though in some\nparticular sorted order and with each line having a specific format).\nIf anyone wants to contribute a \"mdoc\" to \"man\" translator, I'm all for\nit, but I will not try to maintain documents in both formats\nsimultaneously -- whatever support for \"man\" there is, it must be\ncompletely mechanical and automatable.\n\n\nCUSTOM CONFIGURATION OPTIONS\n\nYou may choose to use GNU Zip in preference to the default compress\nprogram as the archive compression too with:\n\n\t./configure --with-gzip\n\nWARNING:  If you have previously configured newsyslog without the above\noption and now wish to add it you will have to remove ./config.cache\nfirst to prevent the wrong program pathname from being used.\n\nBeware that you may need to specify exactly where your syslogd keeps\nit's PID file.  This can be done either by specifying an alternate\ndirectory prefix to ./configure in this way (\"/run/syslog.pid\" will be\nappended to the directory name given):\n\n\t./configure --localstatedir=/var\n\nor by specifying an explicit pathname to ./configure in this way:\n\n\t./configure --with-syslog_pid=/var/run/mysyslog.pid\n\nThe default configuration file location can be modified by specifying an\nalternate directory to ./configure in this way (\"/newsyslog.conf will be\nappended to the directory name given):\n\n\t./configure --sysconfdir=/etc\n\nor by specifying an explicit pathname to ./configure in this way:\n\n\t./configure --with-newsyslog_conf=/etc/newsyslog.conf\n\nTry './configure --help' for more options.\n\n\nFOR MORE INFORMATION\n\nIf you have any troubles, questions, or feature requests, please send\nmail to \u003cbugs@robohack.planix.com\u003e.  The lastest version of this\nsoftware is available at:\n\n\t\u003cURL:ftp://ftp.planix.com/pub/Planix/newsyslog.tar.gz\u003e\n\nor:\n\n\t\u003cURL:ftp://ftp.weird.com/pub/local/newsyslog.tar.gz\u003e\n\n\n-- \n\t\t\t\t\t\tGreg A. Woods\n\t\t\t\t\t\t\u003cwoods-newsyslog@planix.com\u003e\n\t\t\t\t\t\t\u003cwoods-newsyslog@robohack.ca\u003e\n\t\t\t\t\t\t\u003cwoods-newsyslog@weird.com\u003e\n\n\n#ident\t\"@(#)newsyslog:README:HEAD -\u003e master:2025-04-13 14:18:25 -0700:Greg A. Woods:04269ee\"\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frobohack%2Fnewsyslog","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frobohack%2Fnewsyslog","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frobohack%2Fnewsyslog/lists"}