Rolf Neugebauer wrote:
> NB. for achieving higher timer resolutions you might find it
> interesting to look at Soft-Timers at Rice [2]. Events are scheduled
> at the usual timer interrupt frequency but the time wheels are also
> checked at system-call and other interrupt times, thus, depending o
On Thu, Aug 09, 2001 at 12:29:33AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Yar Tikhiy writes:
> : The issue I'd like to submit to discussion is what way to choose:
> : a) Add a command-line option to finger(1) and fingerd(8) telling
> :them not to reveal user information if
In message <[EMAIL PROTECTED]> Yar Tikhiy writes:
: The issue I'd like to submit to discussion is what way to choose:
: a) Add a command-line option to finger(1) and fingerd(8) telling
:them not to reveal user information if the user's homedir is
:protected.
: b) Similar to a), but hide su
On Wednesday, 8 August 2001 at 0:27:23 -0700, Terry Lambert wrote:
> void wrote:
>>> Can you name one SMP OS implementation that uses an
>>> "interrupt threads" approach that doesn't hit a scaling
>>> wall at 4 (or fewer) CPUs, due to heavier weight thread
>>> context switch overhead?
>>
>> Sola
Lo and behold, Yar Tikhiy once said:
>
> In the case of local access, it's no problem, since anyone may read
> /etc/passwd directly. OTOH, letting remote folks peek at user
> information even if the user wants to hide himself is a bad thing.
>
> The issue I'd like to submit to discussion is what
Hello,
[Once I've sent this to -audit, but then was pointed]
[that it wasn't the right list for such a discussion]
Currently, finger(1) reveals user information if the user
has created the ``.nofinger'' file, but his home directory
is unreadable for finger(1).
In the case of local access, it's
Hello,
I was looking through kern_proc.c, and I noticed that unlike pfind,
pgfind does not lock the pointer to a structure being returned,
further investigating showed that the definition fo the pgrp
structure itself, in proc.h, doesn't have a mtx struct defined
within it either.
My proposal is
You have been referred to us to receive a Free Trial Membership to the
first-ever online Tip Club. Tip Club is a local, online sales referral
network whereas you share sales opportunities with members in your
community - online!!!. Some people call them "breakfast clubs", "lead
networks", or "ref
I would very much like to know, exaclty which files comprise the code for
NEWBUS, excluding the drivers themselves.Can anyone help
Thanks a lot,
JAn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ah yes stupid of me.. yes.
On Wed, 8 Aug 2001, John Baldwin wrote:
>
> On 08-Aug-01 Julian Elischer wrote:
> > not from me, though you might say why you want this..
>
> Ever had a panic. Tried to get a dump, and then had lockmgr blow up with
> some other panic? That's what this is tryin
On 08-Aug-01 Julian Elischer wrote:
> not from me, though you might say why you want this..
Ever had a panic. Tried to get a dump, and then had lockmgr blow up with
some other panic? That's what this is trying to prevent. I'll have to make
sure that case is still reproducible, however. Haven
* Brian O'Shea <[EMAIL PROTECTED]> [010808 13:55] wrote:
> On Tue, Aug 07, 2001 at 11:55:47PM -0500, Alfred Perlstein wrote:
> [...]
> > Your system isn't configured for high network throughput, you
> > want to put something like:
> >
> > kern.ipc.nmbclusters=32768
> >
> > this might also help:
On Tue, Aug 07, 2001 at 11:55:47PM -0500, Alfred Perlstein wrote:
[...]
> Your system isn't configured for high network throughput, you
> want to put something like:
>
> kern.ipc.nmbclusters=32768
>
> this might also help:
> net.inet.tcp.tcbhashsize=32768
>
> put those into /boot/loader.conf
S
Wow, much useful feedback. Thanks.
Terry, your general formula for nmbclusters per connection is pretty
much what I am looking for. Great stuff.
> Frankly, it sounds like your application is bad; does it limit
> itself to 150 connections, or is it trying to make as many
> connections as it pos
On Wed, Aug 08, 2001 at 11:17:38AM -0700, Julian Elischer wrote:
> not from me, though you might say why you want this..
I think the reason was in the Subject line:
Subject: [PATCH] Change lockmgr() to not recursively panic
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
not from me, though you might say why you want this..
On Wed, 8 Aug 2001, John Baldwin wrote:
> Any objections to the following patch?
>
> Index: kern_lock.c
> ===
> RCS file: /usr/cvs/src/sys/kern/kern_lock.c,v
> retrieving revis
thanks to all for the help with the timing question. Increasing the hz to
400 (in param.c) allowed for granularity of 5ms, which is what we needed.
For those as unknowing as I was about unix timing, I ran across the
following url which explained why a setting of 400hz allows for a max
resolution
On Wed, 8 Aug 2001, craig wrote:
> I think the performance is the most important in kernel, other
> thing is second. I remember in linux linear address is real
> physical address in kernel space(is it true?). Why freebsd does
> not do in the same way?
1) wouldn't you think things like reliabilit
Any objections to the following patch?
Index: kern_lock.c
===
RCS file: /usr/cvs/src/sys/kern/kern_lock.c,v
retrieving revision 1.46
diff -u -r1.46 kern_lock.c
--- kern_lock.c 2001/04/28 12:11:01 1.46
+++ kern_lock.c 2001/08/07 2
I found an article on livelock at
http://www.research.compaq.com/wrl/people/mogul/mogulpubsextern.html
Just go there and search for "livelock".
But I don't agree with Terry about the interrupt-thread-is-bad
thing, because, if I read it correctly, the authors themself
implemented their ideas in
"Weiguang SHI" <[EMAIL PROTECTED]> writes:
> >From: Alfred Perlstein <[EMAIL PROTECTED]>
> >To: Jeff Behl <[EMAIL PROTECTED]>
> >CC: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> >Subject: Re: timing question
> >Date: Mon, 6 Aug 2001 14:49:55 -0500
> >
> >* Jeff Behl <[EMAIL PROTECTED]> [010806 12:
Hello,
why isn't PFIL_HOOKS kernel compile option listed in NOTES ? If it just
was forgotten, please add it. One trying to compile in ipfilter will get
confused I think.
Regards,
Eugene
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
> craig wrote:
> In general a address in a process is just a linear address which
> refer to physical address indirectly by page directory.
Or a virtual address that does not have a physical page behind
it. Some kernel memory is swappable, and some is overcommitted,
and the pages backing the pag
Brian O'Shea wrote:
> On this machine I run a program which simulates many (~150) simultaneous
> TCP clients. This is actually a multithreaded Linux binary, and one
> thread per simulated TCP client is created. After a few seconds the
> system runs out of mbuf clusters:
>
> # netstat -m
>
> This piece obviously has at least two errors. First, if PAM_OPT_AUTH_AS_SELF
> is true, then value of user is undefined. It should probably log
> pwd->pw_name instead. Second, check for root must of course be reversed
> and become if (!pwd->pw_uid).
Fixed locally. Commit coming soon.
M
--
Mar
Mike Smith wrote:
> Terry; all this "thinking" you're doing is *really*bad*.
>
> I appreciate that you believe you're trying to "educate" us somehow. But
> what you're really doing right now is filling our list archives with
> convincing-sounding crap. People that are curious about this issue ar
It is important for you to send plain-text messages to public lists.
> In general a address in a process is just a linear address which refer to
> physical address indirectly by page directory. This is reasonable in
> user space. However is it necessary to do such thing in kernel? It is sure
>
This is system-specific. Typically, systems only clear memory on
cold-boot, but the behaviour is not standardised.
> As far as I understand, this feature works only if the machine does not
> clear its memory upon reboot. AT compatibles clear memory during the
> BIOS POST, thus, we don't see co
> Matt Dillon wrote:
> > :What "this", exactly?
> > :
> > :That "virtual wire" mode is actually a bad idea for some
> > :applications -- specifically, high speed networking with
> > :multiple gigabit ethernet cards?
> >
> > All the cpu's don't get the interrupt, only one does.
>
> I think th
On Tue, Aug 07, 2001 at 09:33:20PM -0700, Brian O'Shea wrote:
> Hello,
>
> I am using a PIII 550MHz UP system running FreeBSD 4.1-RELEASE. It has
> a 3c905B-TX Fast Etherlink XL card.
>
> # ifconfig xl0
> xl0: flags=8843 mtu 1500
> inet 10.34.24.62 netmask 0xfc00 broadcast 1
Title: ¿¡µà»ç¶û ¸ÞÀÏ ¼Ò½ÄÁö
> I'm developing some code running in kernel that use a lot of stack. And it
> seems i run into stack overflow. This results in some proc structure
> related parts overwrite (particulary p->p_stats->p_timer[ITIMER_PROF]) and
> unexpected signals. (Otherwise, it usually page faults inside
> swi_net
Julian Elischer wrote:
> Who is the expert on apache, modules and shlibs?
> (I'll go offline to discuss the problem if I can find
> an appropriate person.. (can't get ldap module to work with apache
> under freebsd.)
Build Apache from your own sources, and not from ports.
You will also need to u
void wrote:
> > Can you name one SMP OS implementation that uses an
> > "interrupt threads" approach that doesn't hit a scaling
> > wall at 4 (or fewer) CPUs, due to heavier weight thread
> > context switch overhead?
>
> Solaris, if I remember my Vahalia book correctly (isn't that a favorite
> of
34 matches
Mail list logo
