> I've got myself two processes which can't be gotten rid of by SIGKILL:
>
> kkenn 92724 32.0 0.8 5736 356 ?? RN6:25PM 136:52.96 kvt -T Terminal -
> kkenn 1103 0.0 0.0 5740 388 ?? TWN - 0:00.00 (kvt)
>
> (kvt is the KDE 1.1.1 xterm)
>
> I am able to trigger this by at
> On Sat, 24 Jul 1999, Kevin Day wrote:
>
> > For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> > on.
>
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
> 1000 1103 1086 29 75 20
> On Saturday, 24 July 1999 at 20:51:37 -0500, Kevin Day wrote:
> >> On Sat, 24 Jul 1999, Kevin Day wrote:
> >>
> >>> For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> >>> on.
> >>
> Well, theoretically there is nothing wrong going on since you can mount
> things on top of an NFS directory. Mount only complains about
> duplicate normal partition mounts because it can't open the buffered
> block device the second time. NFS doesn't care how many times a
>
>
> To export a single filesystem multiple times, *all* of the attributes must
> be the same. If they aren't the only person you are fooling is yourself,
> since once a filesystem is NFS exported, it is open to the world.
>
> anyway the syntax for what you want is:
>
> /var /var/mails
>
> You misunderstood me. The problem you have is the fact that NFS exports
> are usually limited to the physical mount point of the filesystem being
> exported. Thus it thinks that /var above is the same as /, or that
> /var/tmp is the same as /var if both happen to be in the
>
> :Yeah, I know about -alldirs... The problem was that we had customers who
> :wanted us to export their home directories, and unless I gave them their own
> :filesystem, I couldn't restrict it in the manner i wanted. :)
> :
> :Just checking to see that I wasn't missing a way to do this. :)
> :
At 10:26 AM 8/21/99 +0100, Nik Clayton wrote:
>On Fri, Aug 20, 1999 at 07:34:31PM +0200, Andrzej Bialecki wrote:
> > Both versions are available at:
> >
> > http://www.freebsd.org/~abial/matrix_3.2.tgz
> > http://www.freebsd.org/~abial/matrix_4.0.tgz
>FWIW, there are at least two other
A> Anyway, this module was meant more as a joke, but if you guys like it so
> > much you could vote for putting it in the tree...
>
>What do you mean "vote"? I was waiting for it to show up on my tree
>after a cvsup!
I hate to keep bringing things like this up, or start a legal war, but this
scr
>On Sun, 22 Aug 1999, Andrzej Bialecki wrote:
>
> > On Sat, 21 Aug 1999, Kevin Day wrote:
> >
> > >
> > > I hate to keep bringing things like this up, or start a legal war,
> but this
> > > screensaver is more than likely a copyright and/or tradem
At 06:44 PM 8/22/99 +0200, Andrzej Bialecki wrote:
>On Sun, 22 Aug 1999, Kevin Day wrote:
>
>[trademark violation warning]
>
>Ok, maybe you have a point - I dont know, I'm not a lawyer. But with this
>line of reasoning they could claim that anything using falling letters
> > Is amount of ram available (portably) to configure?
> > So configure could decide to use --low-memory by itself? Allowing
> > overrides, naturally.
> >
> > Leif
> >
>
> There is actually a method to portably guess how much RAM your have available
> from configure -- just write a small C pro
>
> On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote:
> > Here is a patch: (please notice the spelling correction)
>
> Where? I just ran ispell on src/etc/hosts.allow and it didn't catch
> anything.
A more direct patch would have been:
-# NOTE: The hosts.deny file is not longer us
>
> That's odd... I just built it tonight, and I havn't had anything but this:
>
> XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
> XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
> XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
> XFree8
After upgrading from 3.4 to RC2, i'm noticing something that I never saw
before:
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address(state)
tcp0 0 127.0.0.1.4954 127.0.0.1.4242 SYN_SENT
tcp0
>
>
> >
> > Forrest Aldrich wrote:
> >
> > > Is not allowing anonymous ftp logins.
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-current" in the body of the message
> >
> > I noticed this too... Maybe there's too many users, and is refusing
> > c
>
> > After upgrading from 3.4 to RC2, i'm noticing something that I never saw
> > before:
> >
> > Active Internet connections (including servers)
> > Proto Recv-Q Send-Q Local Address Foreign Address(state)
> > tcp0 0 127.0.0.1.4954 127.0.0.1.4242
>
> > Afaik all 3C509B's are PnP. At least here in the UK there is not
> > shortage of those cards.
>
> If I can get a difinitive statement to this effect then I'll grab a
> 3c509B. There was some question as to them actually being PnP though.
>
Yes, the 3c509B can have PnP turned on or off t
>
> On Wed, Oct 06, 1999 at 02:57:23PM +1000, a little birdie told me
> that Peter Jeremy remarked
> >
> > I guess we disagree on this. My feeling is that write activity on
> > root should be minimised to minimise the risk that root will be
> > inconsistent following a crash.
>
> Indeed.
> Thu
> > Kind of complex though. Also the interrupt latency problem is still there.
>
> Not sure that this is as elegant as what you are suggesting , can
> the kernel schedule a user level routine to be executed when an interrupt
> occurs? I guess on Windoze land this is called a driver call-back.
>
>
> > I recently got a quote from a hardware vendor which made the following
> > claim:
> >
> > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip
> > > set which does not support FreeBSD because 16MB of the motherboard
> > > memory is used for the display controller. There
>
> < said:
>
> > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current
>
> The important issue to me is: will FreeBSD work on an 810 motherboard?
> The reason I care is because I need the form-factor (a 1U-high
> server); if I am to use some alternate motherboard, I'll ne
>
> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
> >
> >:>NFS uses the kernel 'boottime' structure to generate its version id.
> >:>Now normally you might believe that this structure, once set, will
> >:>never change. The authors of NFS certainly make that assumption!
> >:
>
> > In message <[EMAIL PROTECTED]>, Kevin Day writes:
> >
> > >Ack, I was using this very same thing for several devices in an isolated
> > >peer-to-peer network to decide who the 'master' was. (Whoever had been up
> > >longest kn
>
> I'm wondering if the AMI MegaRAID controller/driver might be the
> reason that I'm getting a large number of clock resets from ntpd.
> About every half hour, ntpd seems to feel the need to reset the clock
> on the server by about 1/3 of a second. The server has a moderate NFS
> load (going
I'm not sure if this is -current fodder or not, but since it's still
happening in -current, I'll ask.
We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown
on 5.0-current, too). Before, with the exact same load, we'd see load
averages from between 0.20 and 0.30. Now, we're g
> :We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown
> :on 5.0-current, too). Before, with the exact same load, we'd see load
> :averages from between 0.20 and 0.30. Now, we're getting:
> :
> :load averages: 4.16, 4.23, 4.66
> :
> :Top shows the same CPU percentages, ju
> > > I believe the load average was changed quite a while ago to reflect not
> > > only runnable processes but also processes stuck in disk-wait. It's
> > > a more accurate measure of load.
> >
> > Ahh, and since nearly everything is done on this system via NFS, I can
> > imagine th
>
> < said:
>
> > It's probably more accurate, but from a PR standpoint it makes it "look"
> > like FreeBSD is choking under the load, when it really isn't.
>
> Actually, you have it backwards -- it makes it look as if FreeBSD is
> *not* choking under what appears to be a very heavy load
>
I keep getting panics in dqget(ufs_quota.c), with a -current from a couple
of days ago. I think this might be softupdates related, since I can't make
it happen with softupdates turned off, although it's quite possible that it
has nothing to do with it. Does anyone have any idea what might be cau
>
> Hello!
>
> Today I wanted to add a new NFS to my /etc/fstab, but forgot to add it
> to /etc/exports on the server.
> However, I did mount -a several times and always got a "Permission
> denied" for the last one.
>
> Now look what I have here:
>
> Filesystem 1K-blocks
I'm the maintainer for ports/editors/joe, and just tried compiling it under
-CURRENT.
includes which includes ucontext.h
> cc -O -pipe -c umath.c
> In file included from b.h:6,
> from bw.h:23,
> from umath.c:5:
> rc.h:41: conflicting types for `getcontext'
>
I'm the maintainer for ports/editors/joe, and just tried compiling it under
-CURRENT.
includes which includes ucontext.h
> cc -O -pipe -c umath.c
> In file included from b.h:6,
> from bw.h:23,
> from umath.c:5:
> rc.h:41: conflicting types for `getcontext'
>
> On Mon, 22 Feb 1999, Alexander N. Kabaev wrote:
>
> > The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE
> > as of today) to lookup. Shortly after this script is started, all disk
> > activity
> >
> > stops and any attempt to create new process causes system to freese. Wh
> :> :
> :> :This means that invariants need to add relatively little overhead.
> :> :
> :> :Peter
> :>
> :> which they do.
> :
> :You know, guys, for programmers, wanting immediate panics on stuff like
> :this is great, but there isn't one user in a thousand that wants this.
> :If you ma
> On Thu, 1 Apr 1999, Rod Taylor wrote:
> > Just out of curiosity, why are there games included in the FreeBSD
> > source tree?
> >
> > For a group of people that was so worried about including dhcp because
> > it's extra code, don't you think it's time to make those games into
> > ports only?
> >
> :It's not just a matter of turning them off though. A few of the games in the
> :distro are trademark infringements. While the product I'm developing that
> :uses FreeBSD doesn't have the games installed, it brought up the comment
> :from our lawyers "What else are they infringing on that we *are
We had a system running 4.3-RELEASE that I used the sysinstall upgrade
mechanism to upgrade to 5.0-RELEASE. I installed "compat4x" to use our
existing 4.x binaries.
Immediately after rebooting, I noticed most old 4.x binaries were
complaining about "_stdoutp" being an undefined symbol. However
At 11:42 AM 2/2/2003, Jacques A. Vidrine wrote:
On Sun, Feb 02, 2003 at 11:41:32AM -0600, Kevin Day wrote:
> lrwxr-xr-x 1 root wheel 9 Feb 1 00:18 libc.so -> libc.so.5
> lrwxr-xr-x 1 root wheel 16 Jul 5 2002 libc.so.3 -> /usr
At 11:54 AM 2/2/2003, Jacques A. Vidrine wrote:
> Ok, I admit, no matter how it happened, an application using the wrong
libc
> is a bad thing.
>
> But, how are things supposed to work?
Apps that need the old libc.so.4 will find it in
/usr/lib/compat/libc.so.4 (or /usr/lib/libc.so.4 if you didn'
>
> :
> :It should be possible to prevent a user from hogging a system if the system's
> :naive scheduler is improved.
> :
> : Amancio
>
> No, it isn't. For a very simple reason: The resources users need to do
> real work are very similar to the resources users need to hog the syste
> In message <199904102057.paa27...@home.dragondata.com> Kevin Day writes:
> : i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid
> : 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's
> : 40 processes get 50% cpu sha
> yeah the clocks are not setup properly :) but otherwise i'm just
> gonna say HOLY SH*T you fixed NFS! :)
We all owe Matt big for this. :)
> I'm using the default mount operations, as far as NFS server
> not responding messages, i have no clue, but the server is still
> up and i've seen that m
cvsupped last night, and I don't have X installed.
Is this a matter of "If you want to buildworld, install X"? I'm
certain i've done this before though. :)
Kevin
cc -nostdinc -O -pipe -I. -I/usr/X11R6/include -DDISASSEMBLER
-I/usr/obj/usr/src/tmp/usr/include -o doscmd AsyncIO.o ParseBuff
> >
> > To sum it all up is there any difference between the branches?
>
> Yes. We hope that people like you will help us by participating in the
> testing of potential releases _before_ they go out as releases, not
> _afterwards_.
>
> Sitting around doing nothing and then complaining after t
> > I honestly don't know when to bring up things like that, now. :)
>
> For 3.2, _right_now_. What you're doing with Matt is the first stage;
> the next involves bringing it back to the 3.2-beta tree and testing it
> there.
>
> Please understand that if "you" (the community) aren't working on
Matt, I told you about this before, but completely forgot about it. After
doing considerable testing on my test servers, i thought -current was safe
enough to try on our production shell servers. I installed -current on one
of my servers, and to my dismay, it hung. :)
Within 5 minutes of running,
>
> Matt, I told you about this before, but completely forgot about it. After
> doing considerable testing on my test servers, i thought -current was safe
> enough to try on our production shell servers. I installed -current on one
> of my servers, and to my dismay, it hung. :)
>
> Within 5 minut
I'm sure by now Matt is gonna kill me. :)
-current from 2 days ago.
IdlePTD 3096576
initial pcb at 27ea40
panicstr: Out of mbuf clusters
panic messages:
---
panic: Out of mbuf clusters
syncing disks... panic: Out of mbuf clusters
dumping to dev 20001, offset 467137
dump 255 254 253 252 251 2
> :I'm sure by now Matt is gonna kill me. :)
> :
> :-current from 2 days ago.
> :
> :IdlePTD 3096576
> :initial pcb at 27ea40
> :panicstr: Out of mbuf clusters
> :panic messages:
> :---
> :panic: Out of mbuf clusters
>
> This is probably not NFS related unless there is a leak somewhere.
>
>
Erm, sorry guys, that huge message wasn't intended to go back to -current,
just Matt.
My apologies. :)
Kevin
> > :I'm sure by now Matt is gonna kill me. :)
> > :
> > :-current from 2 days ago.
> > :
> > :IdlePTD 3096576
> > :initial pcb at 27ea40
> > :panicstr: Out of mbuf clusters
> > :pan
> :> netstat -m -M vmcore.XX -N kernel.XX
> :>
> :
> :1014/2144 mbufs in use:
> : 714 mbufs allocated to data
> : 300 mbufs allocated to packet headers
> :638/1324/1536 mbuf clusters in use (current/peak/max)
> :2916 Kbytes allocated to network (48% in use)
> :0 requests for memory den
I'm not sure if this is related to the bug I found in 3.1, regarding mmaping
devices, then forking, but with my -current NFS server:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd
257M? :) ps sho
>
> This is normal. It's using a lot of virtual memory. Fortunately, virtual
> memory is cheap.
>
> DS
>
> > I'm not sure if this is related to the bug I found in 3.1,
> > regarding mmaping
> > devices, then forking, but with my -current NFS server:
> >
> > PID USERNAME PRI NICE S
I had two systems reboot at nearly the same time. (30 seconds apart), and
are completely unrelated.
One system was running 2.2.8, and my core file presents me with this:
su-2.02# gdb -k
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show cop
I'm using an Alladin chipset in a -current machine...
CPU: AMD-K6(tm) 3D processor (337.19-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x580 Stepping=0
Features=0x8001bf
real memory = 134217728 (131072K bytes)
avail memory = 126808064 (123836K bytes)
chip0: at device 0.0 on pci0
pcib1
I've got two systems that panic about every 48 hours, saying they're out of
mbuf's. I've tried raising maxusers. (It's at 128 now, but i've gone up to
256 and still seen the same thing).
I believe it's a leak, since it's pretty consistant how long it will stay up
before it runs out.
I've tried r
> On Thu, 27 May 1999, Kevin Day wrote:
>
> > I've got two systems that panic about every 48 hours, saying they're out of
> > mbuf's. I've tried raising maxusers. (It's at 128 now, but i've gone up to
> > 256 and still seen the same th
Grabbed another -current, and are still seeing a few problems yet that Matt
and others haven't solved. I'm not pushing anyone, just reminding that these
are still here, and still problems.
1) The 'inode/vmopar' lockup that Matt is aware of, and apparently tracked
down.
2) Processes starting to
I"m not sure if this is a known problem, but I sent this to the maintainer
of the qt30 port, who suggested I post this here. I couldn't find anything
related in the archives about this problem.
I'm attempting to build qt30 (for kde3) under -CURRENT (ports and
kernel/userland from yesterday).
> On Apr 18, 2018, at 1:42 PM, John Baldwin wrote:
>>
>> Chenged made for it was
>>
>> Index: sys/x86/x86/nexus.c
>> ===
>> --- sys/x86/x86/nexus.c (revision 332663)
>> +++ sys/x86/x86/nexus.c (working copy)
>> @@ -698,7 +698,7 @@
61 matches
Mail list logo
