It can be:
cd /usr/ports
rm -rf */*/work
[]s
On 8/26/06, Rick C. Petty [EMAIL PROTECTED] wrote:
On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
'work' directories !
Removing them one by one was a
Thiago Damas [EMAIL PROTECTED] wrote:
It can be:
cd /usr/ports
rm -rf */*/work
That could overflow your argument verctor if there's a
large number of work directories.
It's better to use echo */*/work | xargs rm -rf if
you don't know the size of the pattern expansion in
advance,
On Fri, Aug 18, 2006 at 10:41:36AM +0300, Martin Eugen wrote:
M I have a simple application, that deals with lots of dgram sockets (UDP).
M Thousands of them. Basically, its purpose is to
M maintain pairs of sockets and when data is received on one of the sockets it
M peeks through it (doing some
Hi all,
has anyone successfully configured pam_krb5? It seems that the ticket
verification that is in the code does not work as intended: I have a host
key in my keytab, but reading it for verification fails, because pam_krb5
constructs the principal name host/[EMAIL PROTECTED] while the
Harti Brandt [EMAIL PROTECTED] writes:
has anyone successfully configured pam_krb5?
I've tested it, but only in a minimal setup.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
On 2006.08.30 16:03:40 +0200, Harti Brandt wrote:
has anyone successfully configured pam_krb5? It seems that the ticket
Hey,
It's being used in the FreeBSD.org cluster, but I never looked at how
it's setup. For the parts I have messed with it just works...
--
Simon L. Nielsen
On Mon, Aug 28, 2006 at 09:01:13PM -0400, Mike Meyer wrote:
I realized today that this one was possible. I suspect it would be
useful to lots of people working on ports, as well as for the sysadmin
stuff I do with it. I'm just not sure where it should goes.
checkdeps.sh
Hi guys,
I hate to open up an already closed can of worms, but I am having a similar
problem with my SimpleDrive also, except that instead of the problem being
such that I can't mount it, instead, when I plug the device into my server,
it detects it and reports it as a umass0 device, but
it detects it and reports it as a umass0 device, but nothing else is
reported. In otherwords, it is not being assigned to a da0 device or
anything of that nature, thus preventing me from being able to mount it.
I'm using FreeBSD 5.4 instead of 4.x. Any suggestions would really help out
9 matches
Mail list logo
