Is there a specific reason why one can not bind portmap to only
the loopback interface?
Portmap has the -h flag, but it automatically inserts 127.0.0.1
to the list if you specify the -h flag.
This prevent one from saying 'portmap -h 127.0.0.1' because it takes
the command line arg's, adds 127.0.0.
On Sun, Nov 17, 2002 at 07:54:48PM -0500, Craig Rodrigues wrote:
> On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote:
> > Hi there,
> >
> > I'm observing very strange memory corruption problems with 2GHz P4
> > system running 4.7 (security branch as of today). Under the load
> > (make
On Sunday 17 November 2002 13:53, Karl Timmermann wrote:
> I'm new to the list and was hoping maybe someone could help me. These
> commands work in Linux (and in this order), but not in FreeBSD/Mac OS X
> as the arp and route commands are different:
>
> arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1
>
Êîìó íàäîåë - ïðîøó ïðîñòèòü!
Òåì, êòî çàèíòåðåñîâàëñÿ GS - ïèøèòå íà [EMAIL PROTECTED] èëè íà ëþáîé èç ðàíåå
óêàçàííûõ àäðåñîâ,
êðîìå yahoo - åãî óæå íåò.
Ñ óâàæåíèåì.
Ðàññûëêà ïðîèçâåäåíà â ñîîòâåòñòâèè ñ ÷.4 ñò.29 Êîíñòèòó
Lyndon Nerenberg wrote:
>
> I've tried a number of syntax-colouring editors, to no avail. The quotes
> (single, double, and back) *are* balanced, according to everything I've
> thrown the script at.
In addition to the other excellent suggestions, I'd suggest using the
syntax highlighting editor,
Brian Reichert wrote:
> > ...basically: mount-less NFS server by IP address, one per IP address.
>
> One server per IP address make sense, but only one filesystem
> exported thusly doesn't. But, I _still_ haven't read the RFCs in
> question, so hopefully I'll see...
No mount protocol = no way to
On Sun, Nov 17, 2002 at 05:36:16PM -0800, Terry Lambert wrote:
> Brian Reichert wrote:
> > Now, I have to go read up on webnfs to find out what webnfs really
> > is...
>
> RFC2054, RFC2055, RFC2755 (not implemented by FreeBSD).
>
> Abstract, RFC2054:
Gee, you beat me to it, by a mile. Thanks fo
Brian Reichert wrote:
> Now, I have to go read up on webnfs to find out what webnfs really
> is...
RFC2054, RFC2055, RFC2755 (not implemented by FreeBSD).
Abstract, RFC2054:
This document describes a lightweight binding mechanism that allows
NFS clients to obtain service from WebNFS-enable
Shouldn't the allocator functions take an additional argument
WAIT/NOWAIT?
Shouldn't the allocator functions also return success/failure that
should be propogated back up to the caller in case they fail?
Shall I take a shot at this or can you Jeff? I'm not sure I'm
comfortable adding an error ca
On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote:
> Hi there,
>
> I'm observing very strange memory corruption problems with 2GHz P4
> system running 4.7 (security branch as of today). Under the load
> (make -j20 buildworld) the compiler or make(1) often die with signal
> 11. I found
I had similar problems. Terry Lambert reports that there is a bug
in the P4. DISABLE_PSE and the other work-arounds mentioned didn't help.
The work-around that worked for me was to use:
options MAXFILES=5
Try that and see if it helps.
Lamont Granquist wrote:
>
> RedHat systems have only two statically linked binaries in their systems
> and it is one of the things that I viscerally hate about RedHat. You have
> to look on another system or lookup on the net which shell to use instead
> of /sbin/init and then play around with a
On Sun, Nov 17, 2002 at 23:16:54 +0200, Maxim Sobolev wrote:
> Hi there,
>
> I'm observing very strange memory corruption problems with 2GHz P4
> system running 4.7 (security branch as of today). Under the load
> (make -j20 buildworld) the compiler or make(1) often die with signal
> 11. I found in
Hi there,
I'm observing very strange memory corruption problems with 2GHz P4
system running 4.7 (security branch as of today). Under the load
(make -j20 buildworld) the compiler or make(1) often die with signal
11. I found in mailing lists that there is similarly looking problem
with -current, any
Hello,
I'm new to the list and was hoping maybe someone could help me. These
commands work in Linux (and in this order), but not in FreeBSD/Mac OS X
as the arp and route commands are different:
arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1
arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1
route add -ne
On Sun, Nov 17, 2002 at 12:39:07PM +0100, Mattias Pantzare wrote:
> Only one filesystem can be WebNFS exported on a computer (that is how
> webnfs works). Remove -webnfs from one.
Jeez - I had no idea that was a factor. You're right; removing
'-webnfs' from the /annex entry allows both filesystem
FreeBSD/x86-64 mailing list
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Dear All
I want to know what is Snoop TCP , and Is it implemented on FreeBSD or Not ?
After I want to know if There is any Performance Enhancing Proxy on the NET
_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join
Ruslan Ermilov wrote, On 11/15/02 09:42:
> How can I list active (i.e. configured with vnconfig) /dev/vn* devices?
>
No way.
Tricky way.
Try to configure each vn device - with NO file name requesting NEGATIVE
size.
If you got EBUSY, the device is configured. If you got EDOM, the device
On Sat, 2002-11-16 at 21:46, Brian Reichert wrote:
> I hope I'm completely misunderstanding the docs for exports(5) and
> kin, but here goes:
>
> The short form:
>
> I have two filesystems I want to export. They're both listed in
> /etc/exports. The first will be exported just fine, the sec
I think you are trying to export the same filesystem to the same list
of addresses twice, so you get an error saying it is already exported.
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Lyndon Nerenberg wrote:
| I've tried a number of syntax-colouring editors, to no avail. The quotes
| (single, double, and back) *are* balanced, according to everything I've
| thrown the script at. That's why I'm more interested in something that
| can actually parse Bourne shell syntax (quiet Terr
22 matches
Mail list logo