Re: FreeBSD Port: openldap-server-2.3.24: default loglevel and /var/log/debug.log

On Sun, Jul 23, 2006 at 06:57:31AM +, Xin LI wrote: > Oh... I think 0 have the same effect with 32768. I think it's Ok to have Sorry, this is incorrect. 0 means disable logging completely, while 32768 means "only the emergency ones", which is recommended in my opinion. Cheers,

Re: FreeBSD Port: openldap-server-2.3.24: default loglevel and /var/log/debug.log

Thierry Lacoste wrote: >> So, Correct, yes. However that loglevel records the activity of the >> server in about the same level of detail as you'ld hope to see from any >> other network server. > With no negative impact on performance for a loaded production server? > My /var/log/debug.log was a

Re: New portmaster version available for testing/feedback

Hans Lambermont wrote: > Doug Barton wrote: > >> Doug Barton wrote: >> >>> I just uploaded a version that has what should be a fix for this, can >>> you give it a try? And thanks for catching this, you're right, it's >>> an oversight on my part. >> I'm curious if you've had a chance to try that fi

Re: portinstall breaks with -m "-j 4"

Mark Linimon wrote: >> BTW, I apologize for this is not at all a portupgrade issue, but an issue >> of the ports system. > > It is an issue with individual ports -- actually not the "port" (e.g. > Makefile framework, pkg-*) but the individual applications (IIUC). > >> Well, at least the ports sys

FreeBSD Port: net/bfilter: rc.d script broken

Hi, I noticed that the rc.d script needs to be renamed to "bfilter.sh" or else it won't be started at boot time (FreeBSD 6.1). I wonder why nobody pointed this out yet, since several other rc.d scripts also miss a ".sh". Or is this intentional? ___

Re: FreeBSD Port: net/bfilter: rc.d script broken

On Sun, 2006-07-23 at 11:39 +0200, Nikolaus Waxweiler wrote: > Hi, > I noticed that the rc.d script needs to be renamed to "bfilter.sh" or > else it won't be started at boot time (FreeBSD 6.1). I wonder why > nobody pointed this out yet, since several other rc.d scripts also > miss a ".sh". Or i

[New Port] KPorts

hi everyone, since a couple of weeks sysutils/kports is now available. it is an advanced KDE-frontend for the ports, designed also at more experienced users, but being being rather easy to use. i justed wanted if any of you have tried it, what impression you got, and if you have any suggestions

Wireshark-0.99.2 build (formerly ethereal)

There are some issues with this port, which used to be known as the Ethereal network analzyer. #1 There is now a dependency on security/libgcrypt which the port needs to be taught about. On 6.1-STABLE, this causes a build failure which can manually be resolved by adding -lgcrypt to the

MASTER_PORT buglet

Dear list, Ahem. Let's try that again with the correct spelling of the list address... The following slave ports are producing an incorrect 'MASTER_PORT' value: emulators/linux_base-gentoo-stage1 (linux_base-gentoo-stage1-2006.0_2) emulators/linux_base-gentoo-stage2 (linux_base-gentoo

Re: portinstall breaks with -m "-j 4"

On Saturday 22 July 2006 22:13, Mark Linimon wrote: > > BTW, I apologize for this is not at all a portupgrade issue, but an issue > > of the ports system. > > It is an issue with individual ports -- actually not the "port" (e.g. > Makefile framework, pkg-*) but the individual applications (IIUC). >

Using >= to check for minimum versions.

Hey guys, Using the minimum version checking is not working for me. using : LIB_DEPENDS=usb-0.1.8:${PORTSDIR}/devel/libusb works. but using the following construct as section 5.7.9 of the porters handbook suggests #LIB_DEPENDS= usb>=0.1.8:${PORTSDIR}/devel/libusb errors out with: ===> V

:(

Добрый день ===> Script "configure" failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the "/usr/ports/textproc/wv/work/wv-1.2.1/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of