On Mon, 27 Nov 2006, Nikolay Pavlov wrote:
Hi. I am trying to extend fstat utility, so that it can use name cache to
recreate full path at least for text. I have found vn_fullpath function
usefull in this case. I am newbe in C, so it could be stupid question, but
could someone explaine what
* Earl Lapus [EMAIL PROTECTED] [2006-11-28 02:41]:
I read that realtime must always be convex. That explains the checking.
However, linkshare and upperlimit can be either concave or convex.
correct
If linkshare(lssc_xx) can be concave then we should allow lssc_m1 to be
less than lssc_m2 even
http://lists.freebsd.org/pipermail/freebsd-hackers/2006-February/015365.html
Who's calling? :-)
Frank
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL
Robert Watson wrote:
Nikolay Pavlov wrote:
Hi. I am trying to extend fstat utility, so that it can use name cache to
recreate full path at least for text. I have found vn_fullpath function
usefull in this case. I am newbe in C, so it could be stupid question, but
could someone
On Tuesday, 28 November 2006 at 16:46:20 +0100, Oliver Fromme wrote:
Robert Watson wrote:
Nikolay Pavlov wrote:
Hi. I am trying to extend fstat utility, so that it can use name cache
to
recreate full path at least for text. I have found vn_fullpath function
usefull in this
Frank Deignan wrote:
http://lists.freebsd.org/pipermail/freebsd-hackers/2006-February/015365.html
Who's calling? :-)
using the everyone knows someone who is closer to the answer than they
are theory, I suggest we forward it to Kirk to forward to Van or Mike.. :-)
(CC'd to Kirk (I think I
Hi,
i have a machine with Pentium 4-D processor utilizing
FreeBSD-6.1-RELEASE-p10/amd64.
The machine is running SMP kernel.
The machine has 2 on-board Broadcom BCM5721 NICs, which are handeled by
the bge(4) driver and 4 D-Link DL10050 NICs, which are handeled
:Nikolay, you might want to have a look at the source code
:of the lsof utility (ports/sysutils/lsof). It is able
:to display path names for file descriptors. Maybe you can
:borrow an idea from it.
:
:It might also be worth mentioning that our friends from the
:DragonFly BSD project (derived
Hello,
Just wondering, abstractly..
-
| A -[socket (UDP)]- B |
-
A creates a UDP socket (call it 's1') to talk to B.
Can B use the same socket ('s2') to talk to A using read(2) or
recv(2), or does A have to accept(2) traffic from B
2006/11/28, Garrett Cooper [EMAIL PROTECTED]:
Hello,
Just wondering, abstractly..
Both sides can read from and write to the socket file descriptor.
You'll need to develop a protocol to determine when either given side
is expecting to receive or to send data (if both sides sit around in
Hello once again,
Just wondering about pthreads now. I know that the lifetime (scope)
of a regular procedural function in C is simple.. it's from the top of
the function body to the bottom of the function body (assuming no
infinite loops are injected). Example:
(void*) function(void*) {/*
On Tuesday 28 November 2006 22:33, Garrett Cooper wrote:
Hello once again,
Just wondering about pthreads now. I know that the lifetime (scope)
of a regular procedural function in C is simple.. it's from the top of
the function body to the bottom of the function body (assuming no
infinite
Devon H. O'Dell wrote:
2006/11/28, Garrett Cooper [EMAIL PROTECTED]:
Hello,
Just wondering, abstractly..
Both sides can read from and write to the socket file descriptor.
You'll need to develop a protocol to determine when either given side
is expecting to receive or to send data (if
Pieter de Goeje wrote:
On Tuesday 28 November 2006 22:33, Garrett Cooper wrote:
Hello once again,
Just wondering about pthreads now. I know that the lifetime (scope)
of a regular procedural function in C is simple.. it's from the top of
the function body to the bottom of the function
On Tuesday 28 November 2006 23:41, Garrett Cooper wrote:
So that means no, after a function's definition is reached the
thread/resources stay in a semi-'alive' (maybe 'zombified') state?, or
does the kernel cleanup / reclaim all of the resources tied up with the
thread?
-Garrett
If you detach
Pieter de Goeje wrote:
On Tuesday 28 November 2006 23:41, Garrett Cooper wrote:
So that means no, after a function's definition is reached the
thread/resources stay in a semi-'alive' (maybe 'zombified') state?, or
does the kernel cleanup / reclaim all of the resources tied up with the
On Tue, Nov 28, 2006 at 04:24:08PM -0500, Devon H. O'Dell wrote:
2006/11/28, Garrett Cooper [EMAIL PROTECTED]:
Hello,
Just wondering, abstractly..
Both sides can read from and write to the socket file descriptor.
You'll need to develop a protocol to determine when either given side
17 matches
Mail list logo
