the string defining the default moved from one file to another in the
last update so the documentation was corrected, but the actual default
was not.
Fix PTHREAD_LIBS support so it works if there's a libpthread installed."
PR: 59268
Submitted by: brooks
to the one delivered with kde, but according to the submitter works a lot better
with russian keyboards
PR: 58616
Submitted by: Rashid N. Achilov <shelton@sentry.granch.ru>
- Fixed bug: ipa incorrectly worked when some IPFW/IP6FW/IPF/PF
rule overflowed and this rule is not the first by order in
the corresponding parameter (in "ipa -t" output), it calculated
more bytes than actually should be calculated
- Fixed two bugs: ipa sometime incorrectly did accounting for
limits if statistics was subtracted in some rule
- Fixed bug: limit's start_time could be yyyy.mm.dd/24:00:00 in
the database, mktime(3) on tested systems understands such
local time and transforms it to next_day/00:00:00, now
start_time can't be 24:00:00 any more and always is
next_day/00:00:00.
- Fixed bug: if new_local_time - old_local_time > one_day (for
example as the result of date of ntpdate commands usage),
then ipa thought that a new day came, now it tries to find out
if local time is changed too quickly
PR: 59209
Submitted by: Andrey Simonenko <simon@comsys.ntu-kpi.kiev.ua> (maintainer)
The clockspeed-conf package provides configuration
scripts to set up a clockspeed client and/or a taiclockd
server using Dan Bernstein's daemontools for supervision
and his clockspeed package for time synchronisation.
Author: Patrick Atamaniuk <atamaniuk at frobs.net>
WWW: http://foo42.de/devel/sysutils/clockspeed-conf/
PR: 51036
Submitted by: Patrick Atamaniuk <atamaniuk at frobs.net>
Freshmeat announcement:
This release has an improved design, improved documentation, the
ability to edit group members directly, support for several password
hashes (CRYPT, SHA, SSHA, MD5, SMD5, and PLAIN), and PDF output for
groups and hosts. A possible error which could delete entries if the
objectclass didn't fit has been fixed. Many Samba 3.0-related bugs,
most related to SIDs, have been fixed.
PR: 58699
Submitted By: MAINTAINER
* integrates a number of FreeBSD enhancements
and fixes a DoS bug
- Respect PTHREAD_LIBS and PTHREAD_CFLAGS [2]
PR: 59049
Submitted by: brooks [1], krion [2]
* The code was reorganized and all the SMTP logic was moved
to its own file.
* CC: works now
* General code cleanup
PR: 58804
Submitted by: Miguel Mendez <flynn@energyhq.es.eu.org> (maintainer)
I found convinient some additional key to the pkg_tree utility,
and I propose to include them. The patches can be placed in
files directory.
PR: ports/46810
Submitted by: Vladimir I. Chukharev <chu@gpi.ru>
Approved by: moi
*** addresses that may be dead, even though the error is temporary:
*** addresses that seem to be dead, but give a hint to a new address:
PR: ports/58694
Submitted by: Oliver Eikemeier <eikemeier@fillmore-labs.com>
The biggest difference between runwhen and other schedulers is that
runwhen doesn't have a single daemon overseeing multiple jobs.
The runwhen tools essentially act as a glorified sleep command.
Perhaps runwhen does nothing that at(1) doesn't, and there are
lots of things at(1) does that runwhen doesn't:
- runwhen doesn't change user IDs - thus it will never run
anything as the wrong user.
- It doesn't keep a central daemon running at all times -
thus it won't break if that daemon dies.
- It doesn't require any modifications to the system boot procedure.
- It doesn't log through syslog(3) - thus it won't make a mess
on the console if syslogd(1) isn't running.
- It doesn't centralize storage of scheduled jobs (or any other
per-job information) - thus unprivileged users can install and use it
without cooperation from root, and without the use of a setuid program
to handle changes.
- It doesn't send output through mail - thus it doesn't break
if there is no mail system installed.
- It doesn't check access control files - thus it doesn't gratuitously
deny users.
Author: Paul Jarc <prj@po.cwru.edu>
WWW: http://multivac.cwru.edu/runwhen/
PR: 58789
Submitted by: David Thiel <lx@redundancy.redundancy.org>
minirsyslogd is a minimalistic, fast and secure (through lack of bloat)
remote-only syslog receiver suitable for hardened log receiver hosts
and/or central log receivers that receive several gigabyte of logs each day.
It will not deal with local syslog data. It does not have a multitude
of configuration, alerting or scripting options. It will however
automatically split inbound syslog data according to IP address,
date and current hour, and do so as rapidly and (I hope) securely as
possible.
Author: Mikael Olsson <mikael.olsson@clavister.com>
WWW: http://www.clueby4.org/minirsyslogd/
PR: 58737
Submitted by: lx@redundancy.redundancy.org
