Hello,
FreeBSD 7.0-RELEASE-p3 #3
$top
...
PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND
36032 root 2838 440 1917M 1493M ucond 0 406:39 3.03% CGServer
...
$cat /boot/loader.conf.local
...
kern.maxdsiz="1073741824"
kern.maxssiz="134217728"
kern.dfldsiz="107
On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote:
> $limits
> Resource limits (current):
> ...
> datasize 1048576 kB
> stacksize 131072 kB
>
> How and why is it possible for process to grow up to 1493M and even
> more? I suppose, it will be able to eat all ava
On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote:
> Hello,
>
> FreeBSD 7.0-RELEASE-p3 #3
>
> $top
> ...
> PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND
> 36032 root 2838 440 1917M 1493M ucond 0 406:39 3.03% CGServer
> ...
>
> $cat /boot/loa
На Thu, 14 Aug 2008 00:44:30 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> записано:
> On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote:
> > Hello,
> >
> > FreeBSD 7.0-RELEASE-p3 #3
> >
> > $top
> > ...
> > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND
> >
Hi.
Looking through man src.conf I found the knob WITHOUT_LIB32 and
recompiled my world with it since I have no use for 32-bit compatibility
on my AMD64. After installworld I realized that /usr/lib32 was still
there and still populated. Searching for information I found this bugreport:
http:
On Thu, Aug 14, 2008 at 09:45:33AM +0200, Morgan Wesström wrote:
> Hi.
>
> Looking through man src.conf I found the knob WITHOUT_LIB32 and
> recompiled my world with it since I have no use for 32-bit compatibility
> on my AMD64. After installworld I realized that /usr/lib32 was still
> there
Thanks for your answer Jeremy :-)
What you've documented above is the Correct Way(tm) to remove lib32
support. Though I advocate people not install it in the first place,
unless they absolutely need it.
I'm not sure I was ever given the option to deselect it during
sysinstall. I don't rememe
On Thu, Aug 14, 2008 at 10:34:26AM +0200, Morgan Wesström wrote:
> Thanks for your answer Jeremy :-)
>
>> What you've documented above is the Correct Way(tm) to remove lib32
>> support. Though I advocate people not install it in the first place,
>> unless they absolutely need it.
>
> I'm not sure
Jeremy Chadwick wrote:
I don't remember if 7.0-RELEASE sysinstall lists it, but I know
7.0-STABLE does.
Oh, that explains it. I installed RELEASE and am still on RELEASE tbh.
Sorry for being on the wrong list... :-/
I don't rememeber any obvious question at least and
/etc/src.conf did not
Thanks Jonathan,
I'm starting to expect it has to be the controller as well. About 20
minutes after I posted this message yesterday (and thus 20 minutes after
ad6 got disconnected - atacontrol list showed "no device present" for
it) the machine crashed while writing to the remaining ad4 drive
On Thu, Aug 14, 2008 at 11:09:23AM +0200, Morgan Wesström wrote:
> Jeremy Chadwick wrote:
>> I don't remember if 7.0-RELEASE sysinstall lists it, but I know
>> 7.0-STABLE does.
>
> Oh, that explains it. I installed RELEASE and am still on RELEASE tbh.
> Sorry for being on the wrong list... :-/
Y
Same thing.
http://lists.freebsd.org/pipermail/freebsd-net/2008-August/019220.html
--
Best regards
Vladimir Korkodinov
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail t
On Wed, Aug 13, 2008 at 03:48:37PM -0400, John Baldwin wrote:
> On Wednesday 13 August 2008 09:42:10 am Kostik Belousov wrote:
> > On Wed, Aug 13, 2008 at 12:22:12AM +, MFC Notification Service wrote:
> > > Dear Konstantin Belousov,
> > >
> > > As you have requested, I would like to notify you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Vogel wrote:
| I have reproduced the problem, you are correct. Thank you for
| persisting thru my doubts :)
Always persisting to help improving FreeBSD. Another odd thing I noticed
today:
When dual-booting Windows on the same machine and doin
On Thu, 14 Aug 2008 14:35:46 +0200
Pascal Hofstee <[EMAIL PROTECTED]> wrote:
> I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to
> update to RELENG_7_0.
>
> I added CPUTYPE ?= core2 to my /etc/src.conf and every call to make
> in /usr/src now gives me the error
>
> "/usr/src/Makef
Hi,
I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to update
to RELENG_7_0.
I added CPUTYPE ?= core2 to my /etc/src.conf and every call to make
in /usr/src now gives me the error
"/usr/src/Makefile.inc1", line 142: CPUTYPE global should be set
with ?=.
*** Error code 1
Anyone has
On Thu, Aug 14, 2008 at 02:35:46PM +0200, Pascal Hofstee wrote:
> I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to update
> to RELENG_7_0.
>
> I added CPUTYPE ?= core2 to my /etc/src.conf and every call to make
> in /usr/src now gives me the error
>
> "/usr/src/Makefile.inc1", lin
On Thu, Aug 14, 2008 at 02:54:41PM +0200, Pascal Hofstee wrote:
> On Thu, 14 Aug 2008 14:35:46 +0200
> Pascal Hofstee <[EMAIL PROTECTED]> wrote:
>
> > I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to
> > update to RELENG_7_0.
> >
> > I added CPUTYPE ?= core2 to my /etc/src.conf an
Jeremy Chadwick wrote:
On Thu, Aug 14, 2008 at 02:35:46PM +0200, Pascal Hofstee wrote:
I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to update
to RELENG_7_0.
I added CPUTYPE ?= core2 to my /etc/src.conf and every call to make
in /usr/src now gives me the error
"/usr/src/Ma
I'm curious about getting my RTL8187 WLAN Usb device to work under freebsd.
Has anyone got a rtl8187 based wlan stick working with freebsd?
As far I know ndisgen won't work because it does not support usb devices.
When I install the windows drivers via ndisgen , there are kernel error
messages rep
At 04:27 AM 8/14/2008, Vladimir Korkodinov wrote:
Same thing.
http://lists.freebsd.org/pipermail/freebsd-net/2008-August/019220.html
Well, that narrows it down a bit since you are not running with Intel
nics. It seems to be in the commits below between
date=2008.07.30.18.00.00
and
date=200
>Jeremy Chadwick wrote:
>> On Thu, Aug 14, 2008 at 02:35:46PM +0200, Pascal Hofstee wrote:
>>
>>> I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to update
>>> to RELENG_7_0.
>>>
>>> I added CPUTYPE ?= core2 to my /etc/src.conf and every call to make
>>> in /usr/src now gives me th
On Thu, Aug 14, 2008 at 10:29:09AM -0400, Mike Tancsa wrote:
> At 04:27 AM 8/14/2008, Vladimir Korkodinov wrote:
>> Same thing.
>>
>> http://lists.freebsd.org/pipermail/freebsd-net/2008-August/019220.html
>>
>
> Well, that narrows it down a bit since you are not running with Intel
> nics. It see
On Thu, Aug 14, 2008 at 04:13:51PM +0200, Johan Hendriks wrote:
> >Jeremy Chadwick wrote:
> >> On Thu, Aug 14, 2008 at 02:35:46PM +0200, Pascal Hofstee wrote:
> >>
> >>> I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to update
> >>> to RELENG_7_0.
> >>>
> >>> I added CPUTYPE ?= co
On Thu, Aug 14, 2008 at 07:36:48AM -0700, Jeremy Chadwick wrote:
> 2) You can use nocona on both i386 and amd64 -- I speak from
> experience. I'm referring to RELENG_7 by the way; I don't think
> nocona is recognised by the base system gcc on RELENG_6.
I stand corrected -- you can use it on RELEN
I'm curious about getting my RTL8187 WLAN Usb device to work under
freebsd. Has anyone got a rtl8187 based wlan stick working with freebsd?
As far I know ndisgen won't work because it does not support usb devices.
When I install the windows drivers via ndisgen , there are kernel error
messages rep
On Thu, 14 Aug 2008, Kevin wrote:
I'm curious about getting my RTL8187 WLAN Usb device to work under freebsd.
Has anyone got a rtl8187 based wlan stick working with freebsd?
Be aware that the RTL8187, RTL8187B and RTL8187L are all different
chipsets. I believe Linux has two drivers for them,
Jeremy Chadwick wrote:
On Thu, Aug 14, 2008 at 04:13:51PM +0200, Johan Hendriks wrote:
Jeremy Chadwick wrote:
On Thu, Aug 14, 2008 at 02:35:46PM +0200, Pascal Hofstee wrote:
I just installed a fresh FreeBSD/amd64 7.0-RELEASE and trying to update
to RELENG_7_0.
I added CPUTYPE ?= core2 to m
> Be aware that the RTL8187, RTL8187B and RTL8187L are all different
> chipsets. I believe Linux has two drivers for them, one driver covers
> two
> chips.
I believe it is the RTL8187L chipset. The actual device is an Alfa Network
"AWUS036H" , product information is
http://dplanet.biz/alfa.com/p
On Wed, Aug 13, 2008 at 05:35:29PM -0700, Gavin Spomer wrote:
> I hope this isn't an invalid topic for this list. I'm on so many lists and I
> hate to join another one just to get help on one thing. Apologies if it's not.
>
> I am able to use ssh-keygen to generate keys so that I can ssh from my
>>> Lyndon Nerenberg <[EMAIL PROTECTED]> 08/13/08 7:10 PM >>>
> You need to start an ssh-agent on the machine you're connecting from and
> populate it with your keychain:
>
> eval `ssh-agent`
> ssh-add
>
> Add the above to your .profile, or check the Linux PAM implementation to
> se
>
>>> Paul Schmehl <[EMAIL PROTECTED]> 08/13/08 7:18 PM >>>
> --On August 13, 2008 5:35:29 PM -0700 Gavin Spomer <[EMAIL PROTECTED]> wrote:
> > I am able to use ssh-keygen to generate keys so that I can ssh from my
> > Mac to any of my SuSE systems or ssh from my Mac to any of my FreeBSD
> > syste
> It's not asking for your password. It's asking for your passphrase to
> decrypt your private key. Are you running an ssh-agent on the Suse
> system?
> --
> R. Kevin Oberman
Aha! Thanks, Kevin. Things are clicking in my brain and I grok now. I just
remembered that when I did ssh-keygen on my m
>
>>> Igor Pokrovsky <[EMAIL PROTECTED]> 08/14/08 8:22 AM >>>
> > ... and I have to enter my password. I've Googled, but can't seem to find
> > the answer to my dilemma. Is it generally kind of a pain to do this between
> > platforms? I'm finally very comfortable on FreeBSD and am starting to
>
On Thursday 14 August 2008 15:29:27 Gavin Spomer wrote:
> >>> Lyndon Nerenberg <[EMAIL PROTECTED]> 08/13/08 7:10 PM >>>
> >
> > You need to start an ssh-agent on the machine you're connecting from and
> > populate it with your keychain:
> >
> > eval `ssh-agent`
> > ssh-add
> >
> > Add the a
Hi Gavin,
On Thu, 14 Aug 2008 08:30:47 -0700, Gavin Spomer <[EMAIL PROTECTED]> wrote:
>>
>
> Uh, not sure. Head spinning now. ;)
>
> 1. I have a Mac, SuSE server and a FreeBSD server.
> 2. I can ssh from my Mac to SuSE server without having to type in my
> password.
> 3. I can ssh from my Mac t
I need to buy this used gear today. Give me a call if you have this or any
other decommissioned Cisco, Nortel, Avaya, Lucent, 3Com, HP, IBM or Sun
Microsystems equipment for sale.
18Units- Used Cisco - WS-X6148-45AF - Will Pay Today At $1100.00 Ea
175 Units- Surplus Cisco - PVDM2-64
I need to buy this used gear today. Give me a call if you have this or any
other decommissioned Cisco, Nortel, Avaya, Lucent, 3Com, HP, IBM or Sun
Microsystems equipment for sale.
18Units- Used Cisco - WS-X6148-45AF - Will Pay Today At $1100.00 Ea
175 Units- Surplus Cisco - PVDM2-64
>
>>> Pollywog <[EMAIL PROTECTED]> 08/14/08 9:32 AM >>>
> On Thursday 14 August 2008 15:29:27 Gavin Spomer wrote:
> > >>> Lyndon Nerenberg <[EMAIL PROTECTED]> 08/13/08 7:10 PM >>>
> > >
> > > You need to start an ssh-agent on the machine you're connecting from and
> > > populate it with your keych
>
>>> Paul Saab <[EMAIL PROTECTED]> 08/14/08 9:41 AM >>>
> look at your permissions in ~/.ssh on the freebsd box. Make sure your home
> directory does not have insecure permissions and .ssh + all the files in
> there are not writable by anyone else.
No worries there. Thanks.
___
That made it possible for me to ssh from SuSE server to FreeBSD server,
but now when I ssh from my Mac to SuSE server it wants a password now:
ssh-agent holds your keys in memory for you, and provides them to remote
systems when needed. You need to run it on each system you log in to.
If you
>
>>> Marian Hettwer <[EMAIL PROTECTED]> 08/14/08 9:43 AM >>>
> Hi Gavin,
> From your Suse, try to run the ssh commando with "-v" or even -vv or -vvv
> to get debugging output.
> If you can't figure out what the debugging output wants to tell you, send
> it to the list.
> But complete, copy 'n' pa
>
>>> Lyndon Nerenberg <[EMAIL PROTECTED]> 08/14/08 9:47 AM >>>
> DOn't you have a local IT helpdesk? This is pretty basic stuff that they
> should have documentation for.
Well, I admit I still have more things to learn, even though I've been the
admin of "my" own Linux servers for 3 years and
On Thu, 14 Aug 2008 19:25:09 +0200, Gavin Spomer <[EMAIL PROTECTED]> wrote:
[snip]
I'm not quite sure right now why you're using rsa keys. I'm always using
dsa keys (ssh-keygen -t dsa). It comes to my mind, that rsa keys are for
ssh version 1, while dsa keys are for ssh version 2.
But I could b
On Thu, 14 Aug 2008 19:31:12 +0200, Gavin Spomer <[EMAIL PROTECTED]> wrote:
Lyndon Nerenberg <[EMAIL PROTECTED]> 08/14/08 9:47 AM >>>
DOn't you have a local IT helpdesk? This is pretty basic stuff that they
should have documentation for.
Well, I admit I still have more things to learn, even
>
>>> Ronald Klop <[EMAIL PROTECTED]> 08/14/08 10:34 AM >>>
> >> I'm not quite sure right now why you're using rsa keys. I'm always using
> >> dsa keys (ssh-keygen -t dsa). It comes to my mind, that rsa keys are for
> >> ssh version 1, while dsa keys are for ssh version 2.
> >> But I could be wron
>
>>> Ronald Klop <[EMAIL PROTECTED]> 08/14/08 10:36 AM >>>
> > Well, I admit I still have more things to learn, even though I've been
> > the admin of "my" own Linux servers for 3 years and FreeBSD for... can't
> > remember, but not quite as long, but I'm not gonna pester my colleagues
> >
Hi Jack,
Thanks for this and for the concise pciconf line. We use em (soon to
be igb) interfaces extensively at work.
Best,
George
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
Sebastiaan,
Have you tried connecting your 250GB drives to the troublesome
controller? If so, does "stressing" them cause the system to panic?
~Cian Hughes
--
University of Bristol Medical School
On 14 Aug 2008, at 10:37, Sebastiaan van Erk wrote:
Thanks Jonathan,
I'm starting to expect it
I fought with this issue all day today, trying to root cause it, and while I
don't have a solution I do have a better understanding of it.
I was wrong about it being the interrupt handler, at least if there's any
issue with it its not the primary cause. I actually found out using a
Fedora Live CD
50 matches
Mail list logo
