Hi ...
Without starting the racoon daemon and doing a secure connect
everything works fine without a problem. If I start racoon,
do a tunnel connection and then run daily, the machine panics ..
Reinier
On 16-Sep-00 Shoichi 'Ne' Sakane wrote:
I'm running a current machine of 12 Sept although
As far as I recall ... the first kernel was before any of the SMP
commits ... but in case it was not ... how do I go about
going back to a "coarse grain lock" kernel ... can I set
something in the config file or do I have to checkout old
sources ??
Reinier
On 17-Sep-00 [EMAIL PROTECTED] wrote:
On Sun, 17 Sep 2000, John Baldwin wrote:
...
Hmm, could it be lockmgr() related?
How can I proof?
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Updated around 3 am (CET) and tryed to build the world but if fails
miserably on libedit.
Script started on Mon Sep 18 06:18:48 2000
(root@worldclass:/usr/src) make world
--
elf make world started on Mon Sep 18 06:18:52 GMT 2000
On 17 Sep, John Polstra wrote:
What is the point of that change? Functionally it makes no difference
at all, since "*auth" is an AuthenticationConnection. It makes the
I was a little bit confused at that time. Yes, it's more of a bikeshed
decision, IMHO it makes it less difficult to read
On Tue, Sep 12, 2000 at 04:44:41PM +0200, Reinier Bezuidenhout wrote:
Let me first ask ... do you use the "suspend/resume" option??
Yep.
This caused the same "lockup" every few seconds on my machine too -
a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted
it worked fine.
I
On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
I recently ran into revelant problem with /dev/stdout, while
working on some software under linux that expected /dev/stdout as an
argument instead of using stdout.
Using the device file breaks, if the process is suid to a
-On [2916 17:10], Alexander Leidinger ([EMAIL PROTECTED]) wrote:
after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf.
I fixed this in the old version, but it seems the bug is back.
I have a look at it and try to produce a patch again.
You mean that bug which you reported
"current machine" meaning FreeBSD-current? if so, are there any
locking behavior changes due to the introduction of fine grain locks?
what happens if you go back to coarse grain lock kernel?
As far as I recall ... the first kernel was before any of the SMP
commits ... but
Without starting the racoon daemon and doing a secure connect
everything works fine without a problem. If I start racoon,
do a tunnel connection and then run daily, the machine panics ..
I bet you can panic the kernel with setkey(8) in that case. am I
correct? if so,
On 18 Sep, Jeroen Ruigrok van der Werven wrote:
after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf.
I fixed this in the old version, but it seems the bug is back.
I have a look at it and try to produce a patch again.
You mean that bug which you reported and produced a
-On [2918 16:20], Alexander Leidinger ([EMAIL PROTECTED]) wrote:
On 18 Sep, Jeroen Ruigrok van der Werven wrote:
You mean that bug which you reported and produced a patch and which I
subsequently committed? The malloc.conf - AJ resulted coredump one?
Initially yes, but at the moment I'm
Does anyone have any clue what could cause errors like this? I've
been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure
there's more information I should be giving, so just let me know what to
find. dmesg is at the end.
Sep 18 07:56:01 lithium last message repeated 17 times
Sep
On 18 Sep, Jeroen Ruigrok van der Werven wrote:
You mean that bug which you reported and produced a patch and which I
subsequently committed? The malloc.conf - AJ resulted coredump one?
Initially yes, but at the moment I'm under the impression it's another
bug (I don't know where it is and
On Mon, 18 Sep 2000 10:00:53 +0200 (SAST)
Reinier Bezuidenhout [EMAIL PROTECTED] said:
rbezuide As far as I recall ... the first kernel was before any of the SMP
rbezuide commits ... but in case it was not ... how do I go about
rbezuide going back to a "coarse grain lock" kernel ... can I set
Hi,
It seems that due to unknown for me reasons, thread-safe wrapper for
fpathconf(2) syscall is missed from the libc_r, while fpathconf listed in the
list of syscalls for which thread-safe wrappers are to be provided
(src/lib/libc_r/Makefile:31). The following short example exposes the bug:
On Mon, 18 Sep 2000, Ben Smithurst wrote:
Does anyone have any clue what could cause errors like this? I've
been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure
there's more information I should be giving, so just let me know what to
find. dmesg is at the end.
On Mon, 18 Sep 2000, Ben Smithurst wrote:
Does anyone have any clue what could cause errors like this? I've
been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure
there's more information I should be giving, so just let me know what
to find. dmesg is at the end.
...
ep0:
Does anyone know if the patch indicated below was committed to fix this
FreeBSD 3.2 bug? I can't upgrade to a later release yet, but if this patch
is it, I can hack it in.
On Mon, 11 Sep 2000, Alfred Perlstein wrote:
* David Kirchner [EMAIL PROTECTED] [000911 12:19] wrote:
Yes, there's a
Alright, I've been using -CURRENT with the SMPng changes for a few days
and wanted to give some feedback.
Overall everything works, although I have been experienceing a few
problems which may or may not be related.
1) When I'm playing music (mp3), and I move the mouse or move a window in
X,
It seems that recent (the last two weeks?) changes to periodic have
changed things so that non-root users of it no longer get any output.
A simple fix would be to change the default output to $USER (not yet
tested). However, having a user-specific periodic.conf would be a lot
more useful. But I
On Tue, 19 Sep 2000, Bruce Evans wrote:
On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
I recently ran into revelant problem with /dev/stdout, while
working on some software under linux that expected /dev/stdout as an
argument instead of using stdout.
Using the device file
On Sun, 17 Sep 2000, Doug Barton wrote:
If I use the buildkernel target I get the following:
make: cannot open
/usr/amd/realmounts/slave/usr/current/src/sys/dev/aic7xxx/Makefile.
*** Error code 2
Stop in /usr/amd/realmounts/slave/usr/current/src.
*** Error code 1
This is
This is still broken:
=== aac
cc -O -pipe -DAAC_COMPAT_LINUX -D_KERNEL -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
-I. -I@ -I@/../include
Et voila.
Thanks,
Doug
On Mon, 18 Sep 2000, David Greenman wrote:
Here is a fix. Hopefully Mike will commit it soon.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
President, TeraSolutions, Inc. - http://www.terasolutions.com
Pave the road
I've seen these patches many times and think that it is a good idea.
This interface needs to be exported so that the pccard system sounds
don't interfere with normal systme sounds.
Thanks for your response. OK, I will commit this patch the next
weekend.
--
By the way, we also need
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
: I've seen these patches many times and think that it is a good idea.
: This interface needs to be exported so that the pccard system sounds
: don't interfere with normal systme sounds.
:
: Thanks for your response. OK, I will commit
Warner-san wrote:
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
: I've seen these patches many times and think that it is a good idea.
: This interface needs to be exported so that the pccard system sounds
: don't interfere with normal systme sounds.
:
: Thanks for your response. OK,
28 matches
Mail list logo
