Previous history for syslog-ng version 3 can be found in sysutils/syslog-ng3.
Suggested by: syslog-ng upline and syslog-ng version 1 maintainer.
Approved by: syslog-ng version 1 maintainer and syslog-ng version 3 maintainer
2 weeks according to portaudit (ranging from 23 days to 7 years).
The maintainers were notified by mail that this action would be taken
on 2011-09-03. (Ports for which maintainers responded have been/will be
dealt with separately.)
Also mark DEPRECATED ports that rely on the FORBIDDEN ports, and a few
ports that rely on those DEPRECATED ports.
- Break line at 80 chars in pkg-descr
- Remove LDFLAGS from CONFIGURE_ENV
PR: ports/161003
Submitted by: Ruslan Mahmatkhanov <cvs-src@yandex.ru> (maintainer), Michel Talon <talon@lpthe.jussieu.fr> [1]
When mode_t is char- or short-like, it will be promoted to the pure
int when it is passed as the variable argument [1], so we should pass
'int' to the va_arg.
I had also eliminated fflush for the stream opened read-only, since
it will always fail and there is no need to flush read-only streams.
[1] http://c-faq.com/~scs/cclass/int/sx11c.html
Feature safe: yes
PR: 152304
2011-09-01 sysutils/wots: No more public distfiles
2011-09-15 sysutils/gpart: Upstream disappeared
2011-09-01 sysutils/plod: No more public distfiles
2011-09-01 sysutils/checkservice: BROKEN for more than 6 month
2011-09-01 security/nsm-console: BROKEN for more than 6 month
2011-09-01 security/fressh: No more public distfiles
2011-09-01 palm/pose: No more public distfiles
2011-09-01 palm/isilo: No more public distfiles
2011-09-01 news/ija: BROKEN for more than 6 month
2011-09-01 news/PicMonger: Abandonware
Thanks to Rudolf Polzer and Justin Head!
PR: ports/157176
Submitted by: Rudolf Polzer <rpolzer@mucke-novak.de>
Approved by: Justin Head <ports@encarnate.com> (maintainer)
Unix provides the standard du utility, which scans your disk and tells you which
directories contain the largest amounts of data. That can help you narrow your
search to the things most worth deleting.
However, that only tells you what's big. What you really want to know is what's
too big. By itself, du won't let you distinguish between data that's big because
you're doing something that needs it to be big, and data that's big because you
unpacked it once and forgot about it.
Most Unix file systems, in their default mode, helpfully record when a file was
last accessed. Not just when it was written or modified, but when it was even
read. So if you generated a large amount of data years ago, forgot to clean it
up, and have never used it since, then it ought in principle to be possible to
use those last-access time stamps to tell the difference between that and a
large amount of data you're still using regularly.
agedu is a program which does this. It does basically the same sort of disk scan
as du, but it also records the last-access times of everything it scans. Then it
builds an index that lets it efficiently generate reports giving a summary of
the results for each subdirectory, and then it produces those reports on demand.
WWW: http://www.chiark.greenend.org.uk/~sgtatham/agedu/
-D option which has been added to the rc.d script) retry failed DNS lookups;
this is useful in case spiped is launched before DNS resolution is working.
With hat: maintainer
