Greg Lehey wrote:
> On Wednesday, 30 June 1999 at 17:56:33 -0700, Matthew Dillon wrote:
> > So far I've run the latest buffer cache related fixes overnight on my
> > SMP test box without any problems.
> >
> > Is anyone still experiencing buffer-cache related problems with CURRENT
?
Is there any way to specify a realm with whitespace to fetch? I've
just had a fun time trying to do:
% export HTTP_AUTH="basic:SunSolve Online:x:y"
% fetch -v http://online.sunsolve.sun.co.uk/whatever
senddoc: cannot authenticate with server
Looking at the code it appears that there isn't a way
< said:
> % export HTTP_AUTH="basic:SunSolve Online:x:y"
> % fetch -v http://online.sunsolve.sun.co.uk/whatever
> senddoc: cannot authenticate with server
> Looking at the code it appears that there isn't a way to escape the
> whitespace...
That's probably correct. You're certainly welcome to
Hi,
This following is a patch that eliminates the sysinstall prompt that
informs you that a distribution has failed to install, when really
everything worked OK.
This problem can be a real pain on FTP installs when you have packages
following the normal install (like you can set up for a scripte
:
:The main place I expect there to be trouble with is the swap-backed-vn device
:code. It does it's own clustering, aync/async-aware IO chaining, etc.
:
:> Greg
:
:Cheers,
:-Peter
I'm getting a new one. Sometimes during booting or rebooting the system
gets stuck in "biord". I have not
The Rfork man page says:
RFMEM If set, the kernel will force sharing of the entire ad-
dress space. The child will then inherit all the shared
segments the parent process owns. Other segment types
will be unaffected. Subsequent forks by the parent wi
Yes, you are absolutely right.
It should also say: rfork() cannot be directly called from C when used
with RFMEM, because C cannot deal with the fact that both processes
return to the same stack.
( As an aside, we really need a linunx clone()-like system call so we
ca
panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 1 Jul 1999, Matthew Jacob wrote:
>
> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
>
It might be if you supplied some additional information, like what
sources your kernel was built from, as a minimum. UP or SMP? What
was the box doing when it paniced? If you
> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
I had the similar panic last night during make world. I have a
dump at home but I didn't have time to take a look this morning.
My system is dual PPro SMP, 128MB RAM, 3 SCSI UW disks with CCD,
about two day old -current. Sinc
>
> >
> > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
> >
Sorry- -current as of today, alpha. rebooting. Likely an NFS lock.
>
> It might be if you supplied some additional information, like what
> sources your kernel was built from, as a minimum. UP or SMP? What
>
I'm about to install FreeBSD 3.2 on a machine with an IBM-DJNA-371350
(Deskstar 22GXP 13.5GB) drive. I see that on the -current mailing
list a few weeks ago you (phk) said:
>Try disabling "ultra DMA" in the BIOS, that seems to have worked for
>me on my IBM-DJNA-371800 drive.
Is that relevant fo
I'm getting some really odd stuff with recent -current's configured
for SMP. Processes are getting stuck in getblk() and other I/O waits.
It does not appear to occur with UP configuration, only SMP.
I seem to be able to repeat the problem by dd'ing a raw partition from
a SCSI
:interrupts such as clk and rtc continue to work just fine.
:
:When the interrupts stop, dd is stuck in a disk-wait state. I'm sure it
:isn't the SCSI bus: I've got three SCSI busses and it occurs on all three.
:Plus it does not occur on a UP kernel, only an SMP kernel.
:
:If
14 matches
Mail list logo
