.
The device is a name such as cd0 or mcd0.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
can't find a function which returns this
data to a user land application. Is this possible? If so how?
Take a look at /usr/src/usr.sbin/vmstat.c. You'll want to use sysctl()
to pull the vm.vmmeter data block, which is of type struct vmmeter.
--
Dan Nelson
[EMAIL PROTECTED
are usually due to an excessively
overclocked CPU, or bad RAM. Try dropping your CPU speed 5%.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
one (say for /), you may not be
able to kill the other process without rebooting.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
a vnode lock and then be usurped for processor?
System calls aren't preempted, but if while processing a syscall, the
kernel decides to tsleep(), say because of disk I/O (a very common
thing when dealing with vnodes :), then another process is free to
start running.
--
Dan Nelson
with the
people on the Squid mailing-list: [EMAIL PROTECTED]
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
'tty[pqrsPQRS]' | wc -l
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
In the last episode (Feb 20), Cliff Sarginson said:
On Tue, Feb 19, 2002 at 02:58:09PM -0600, Dan Nelson wrote:
In the last episode (Feb 19), Cliff Sarginson said:
Hello,
Someone suggested this may be the right list for this.
- Has consideration in the loadable modules
will automagically load modules it depends
on to run ?
See the module(9) and MODULE_DEPEND(9) manpages.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
-1001057530]:
count=1024
[ ... ]
Dump should ideally be run on an unmounted filesystem. The next best
is to create a snapshot ( /usr/src/sys/ufs/ffs/README.snapshot ) and
dump that.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
into FreeBSD without using DOS (have grub load
/boot/loader which in turn loads the kernel).
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
the rate drops?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
-current
or, easier to read the entire thread:
http://groups.yahoo.com/group/freebsd-current/messages/39583?threaded=1
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
!= * ] ; then
for i in $FILES ; do $HOME/scripts/test-freebsd-cvs.sh $i ; done
fi
done
it looks fine.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
of them and put them in intel/compiler50/ia32/substitute_headers.
You'de have to do the same for any offending FreeBSD headers.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
to rebuild the kernel, and a binary search should let you narrow it
down in under 2 hours, I'd say. I would have suggested looking at
Alfred's SMP file locking commit on 2001-01-13, but if your program
just does malloc()s it shouldn't be affected by that.
--
Dan Nelson
[EMAIL PROTECTED
) of the things
sar would need to measure. The only problem is writing sar, sa1, sa2,
and sadc. If you don't mind the GPL, the Linux systat package includes
an implementation of sar. In 1999, SCO promised to release their
source under MPL, but never did.
--
Dan Nelson
[EMAIL PROTECTED
, they published a press release saying they would, but the web
page referenced in the announcement never had any download links, and
is now 404.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
fsck is using to grow and fill up
the filesystem. Unlikely, but possible if your disk is almost full
already.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
the overhead of the TCP stack if
you're not leaving your own ethernet?
You should be able to easily saturate a 100mbit link with FreeBSD 4.*
machines, and I can do 15-20MB/sec with Netgear GA620 gigabit nics (SMP
2 x pIII/600).
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail
/Makefile ,
make obj make depend make make install.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
the info distribution checkbox in sysinstall?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
In the last episode (Oct 16), Andrew Reid said:
On Mon, Oct 15, 2001 at 04:22:21PM -0500, Dan Nelson wrote:
In the last episode (Oct 15), j balan said:
Does anyone know the command to reload rc.conf
'reboot' is the only sure way.
That's a bit of a problem as far as I'm concerned
;
mib[1] = KERN_MAXPROC;
len = sizeof(maxproc);
sysctl(mib, 2, maxproc, len, NULL, 0);
Note: always compile your programs with -Wall. gcc would have flagged
this as:
test.c:18: warning: passing arg 4 of `sysctl' makes pointer from integer without a cast
--
Dan
0 discarded for bad checksums
udp:
127972686 datagrams received
0 with bad checksum
ip:
26765 total packets received
0 bad header checksums
Each counter has probably rolled over at least 5 times (I have to ask,
why aren't these 64 bit counters?)
--
Dan
an MTU of 576 bytes on that route and doesn't try anything
larger in future. This would be great *except* that I'm trying to
turn the whole thing into a factory for ICMP cannot fragment
messages. Is there a simple way to flush the route-mtu table on the
server?
--
Dan Nelson
[EMAIL
.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
.globl printasint
.type printasint,@function
printasint:
pushl %ebp
movl%esp, %ebp
subl$16, %esp
pushl 8(%ebp)
pushl $.LC0
callprintf
leave
ret
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe
enough that I couldn't keep it working.
I didn't have any problems with it in the couple of years I had it on
my system.
There was a post in June on the -net mailinglist from a guy that is
working on getting SACK into -STABLE, so there's hope yet.
--
Dan Nelson
[EMAIL PROTECTED
off the BSD ftp
source; you're looking for evidence that the kernel itself has BSD
stack code in it, right?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
, or tell me
why this can't be done, i'd be very thankful. :)
Would dladdr() do what you want?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
for this, they will
try to start up again.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
.endif
In other words, would adding '-R' hurt?
If you are accessing a local CVS repo that you have updated via cvsup,
no. But if you are accessing something on freefall directly, I think
you need the locking just in case someone is committing at the same
time.
--
Dan Nelson
In the last episode (May 21), Beech Rintoul said:
I'm trying to do an install and I keep getting an error 70. Can someone
please tell me what that is?
Error code 70: Stale NFS file handle
If you have any NFS mounts, try dismounting and remounting them.
--
Dan Nelson
? If init can't spawn a getty, it
usually logs it.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
the reasons :)
Probably because the coders are waiting for SMPng to stabilize a bit
before working on threads. Once work starts, it will be visible to all
in CVS, just like SMPng is now.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
| grep ftime
ftime.o:
T ftime
for some reason you forgot to include your compile line and the error
message you got.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
going through
it, though. Since the router doesn't know the capabilities of the 2nd
host at the time it proxies the connection from the 1st, you can't
negotiate any enhanced TCP features like SACK or rfc1323 (window
scaling or timestamping).
--
Dan Nelson
[EMAIL PROTECTED
ce. For non-techies,
it is perfect. They have heard of Unix, and know that Linux is one of
the more popular unix-type OSes.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
correctly ensure
consistency while reading in data ... ?
As long as everything that touches your mailboxes use dotlocking,
you should be safe. Use procmail as your local mailer, and make sure
your mailreaders use dotlocking.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send
own system while writing this. [1]
It's sort of misfiled:
$ cat /usr/ports/devel/mob/pkg-descr
This is a port of mob, that tries to figure out memory system
characteristics at run-time.
$
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
. The pages may be clean or dirty.
[snip excellent explanation]
Hey, can we get this into a manpage, like vm(9) or something? Jesper's
question is definitely a FAQ, and it'd be nice to point people to some
official documentation.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail
In the last episode (Mar 01), jett tayer said:
can ipchains / iptables be ported to FreeBSD... this is a suggestion
if u dont mind.
We've already got ipfw and ipfilter; why in the world would we need a
third packet-filtering systam? :)
--
Dan Nelson
[EMAIL PROTECTED
or "options NMBCLUSTERS" and rebuild your kernel.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Cisco's documentation, and it doesn't look
like FEC is anything beyond plain old trunking (with the option of
autoconfiguration on some hardware). As long as you configure the
appropriate ports on the switch on the other end as "SA-Trunk", or
"Trunk", you should be okay.
--
is running by looking at the output of the
"mount" command:
/dev/da0s1f on /usr (ufs, NFS exported, local, soft-updates)
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
r.
Or it might need to be setuid for some other reason, since OpenBSD runs
their crontab setuid root, and they usually are pretty
security-paranoid.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ent timing values
for each clock with "sysctl machdep | grep freq".
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
on /usr fails? Other than that, I love the idea!
Force-mount it read-only if necessary, or simply copy a static sshd
into /sbin. Runnning fsck -y is the wrong solution, since if fsck
can't fix an error automatically, something pretty bad has happened
(physical media error, someone dd'ing onto the
new mail is delivered?
That's why dotlocking is recommended for locking mail spools. Both
procmail and mutt will dotlock your mail file while it's being
accessed.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
around and
tells you what mutex a process is waiting on. It replaces "MUTEX" with
"M##", where "##" is the first 6 characters of the mutex name
passed to mtx_init. At the moment all I see is "MGiant" all over the
place, but hopefully that'l
ork. It's important to pick
a file that has existed since the tree was created, since any tags laid
down before the file was created won't show up (get status on
Makefile.inc1 as a comparison).
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
Followups to -emulation, please
In the last episode (Nov 21), Walter C. Pelissero said:
Dan Nelson writes:
In the last episode (Nov 20), Walter C. Pelissero said:
I'm trying to run a SCO SVR4 executable on FreeBSD but I get a
SIGSYS (invalid system call) at the very beginning. Here
, which will
turn it off, then setting it back to normal when you want to turn it on
again:
off: ESC [=16;15C ESC [=3C
on:ESC [=15;16C ESC [=3C
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" i
is really 720x400 pixels if you want to
keep track. If you want more lines/columns on the console, see the
vidcontrol manpage.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
to be running. In
other words, Don't Do That. Sorry.
You can make it look like you're switched to vty 0, by making your
screen_saver() function simply copy the contents of vty 0 to screen
memory on every update. Just make sure both vtys are the same size
first...
--
Dan Nelson
[EMAIL
But remember that this simply lists what IRQs active drivers in teh
system think the hardware uses. PCI and ISA-PnP devices can tell the
system what their IRQs are, but when you have to deal with legacy ISA
cards you really don't have a good way of figuring out what IRQs they
use.
--
Dan
So if you're running completely diskless, or had
NFS-mounted home dirs, for example, you can still use fifos.
Your example works if you run both lines on the client, or both on the
server.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
In the last episode (Oct 06), Paul Herman said:
On Fri, 6 Oct 2000, Dan Nelson wrote:
I think that's expected behaviour. Fifos should be usable on NFS
mounts, but an active fifo is only usable for processes running on
the same machine.
That's cool, seems reasonable.
BTW, the hanging
characters.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
o this all the time to programs that I *don't* want to
attach directly to with gdb.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
values rise after the machine has been on for
long periods of time.
ports/sysutils/healthd should do the trick.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ALLOC PROBLEMS" section.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
way.
Figure out how pstat -T does it:
$ pstat -T
294/3240 files
0M/1173M swap space
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
t mutually exclusive, though. What about game CDs that have
a filesystem on track 1 and music on the other tracks?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
and
return the requested data.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
, they can add the flag
themselves. Besides, the default scheme is unreadable on the console
anyway (blue and purple and red on black? what were they thinking?)
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" i
, so
the only way to do it now is to start up packet filtering. Why do you
need to turn it on?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
activity the web servers will
be doing, and with either of those enabled, ipfilter should be able to
process the packets. I've never used ipfilter myself, though, so I
can't say whether this will definitely work or not.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail
a ksh developers list
then.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
not sure what local() and getint() are, since you didn't include
the source to them, but you should probably be using the getenv() and
putenv() functions to read environment variables.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
:34:46 hp8100mp1 printer: paper jam
Jun 9 10:35:12 hp8100mp1 printer: error cleared
Jun 13 08:14:43 hp4000sa printer: paper out
Jun 13 08:14:43 hp4000sa printer: error cleared
so, they are already tagged.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
previously
mentioned.
That documentation is misleading, then. The hostname is definitely not
looked at. See syslogd.c, the logmsg() function.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Directory simtelnet/msdos/microsft/
FilenameType Length DateDescription
===
pd0646.zip B21113 921209 Updated CHKDSK.EXE UNDELETE.EXE for DOS 5.0
$
Try one of those, from your favorite Simtel mirror.
--
cument any of this. You have to root through headers trying to
figure out what structures are used when.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
g. I don't know how hard it would be to
add, either. You'll probably have to ask -hackers about that (cc and
reply-to reset there).
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In the last episode (Jun 08), Mark Newton said:
Ok -- I envisaged that there'd be a difficulty with different SysV
vendors who used different semantics for the same syscalls, or
different syscall numbering schemes. "It could happen!" (and, as we
can see, it probably has).
Possibly.. But
() and fstat()
work.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
7
apparently has two additional syscalls: lseek32 and lseek64, but I
don't know what numbers they are; I don't have UW7.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I had patterened my code after a free version of truss for Digital
Unix.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
-w logfile.txt", I drop no packets.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
rogram die on an unexpected divide by zero than
continue with invalid data.
Why should we treat (1.0/0.0) any differently from (1/0)?
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
d queueing,
update PR kern/10398.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:)
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
a large file, I see commits
too (a 64K commit every 128K or so on my system). Mounting another
FreeBSD box, I see absolutely no commits at all.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" i
in /etc/login.conf .
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
not a stock
FreeBSD program.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
-.
)
20 pps- 20 pps - 20 pps -'
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
2TB worth of storage on a pair of Sparcs, and
we probably could have created two 1TB filesystems. We went with 200gb
and 100gb volumes instead, for ease of backup.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
. I'd say
that most database-backended servers have a similar problem, and do
have per-IP query limits or some other form of restrictions. The best
(worst?) example of this I can think of is the all-too-common IIS
"HTTP/1.0 Server Too Busy" message.
--
Dan Nelson
of mbufs a couple times because I had
a lot of backed-up FTP connections over a T1 link.
Easiest way to determine what you need is to just let the system run
for a while, and then rebuild the kernel with your NMBCLUSTERS set at
your peak value + 50% .
--
Dan Nelson
[EMAIL PROTECTED
:) Although if you are already at your peak load
for the day, you might be okay.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
rface, and "man ch" for the C autoloader interface.
cat /dev/rsa0
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
variable, there's not much you
can do about it under Unix. And I'll not even mention what happens to
this when you start swapping.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In the last episode (Jan 19), Charles Sprickman said:
On Tue, 18 Jan 2000, Dan Nelson wrote:
The handbook instructions are for kernel-generated panics; for a
manual panic like yours, the stack is unimportant. The easiest way
to see which processes are active is to run this:
(kgdb
796K 1040K ttyin0:00 0.04% 0.04% tcsh
24537 inch_hom 2 0 640K 872K sbwait 0:00 0.04% 0.04% httpd-1.3.3-us
You're running a different httpd here. Try moving the binary from this
machine over to the other one and see if the loadavg drops.
--
Dan Nelson
In the last episode (Jan 18), spork said:
On Tue, 18 Jan 2000, Dan Nelson wrote:
In the last episode (Jan 18), spork said:
I'm not sure what the problem is. You're 97% idle. Maybe the hosted
web sites on this machine are slightly more active than the ones on the
other box. You
In the last episode (Jan 18), spork said:
On Tue, 18 Jan 2000, Dan Nelson wrote:
CTRL-ALT-ESC, and at the prompt type in 'panic'. You'll need DDB
compiled into the kernel, and crashdumps enabled.
By now, you should know my next question... What am I looking at? I
built a kernel
it was running
2.2.7 or 3.0, but it was definitely FreeBSD, running a standard ircd.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
var=MixedCase
lvar=${var:l}
echo $lvar
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
301 - 400 of 432 matches
Mail list logo
