Re: Determining Ram

2003-02-04 Thread Mike Meyer
In <[EMAIL PROTECTED]>, Doug Reynolds <[EMAIL PROTECTED]> typed:
> On Sun, 2 Feb 2003 20:02:30 -0600, Mike Meyer wrote:
> >In <[EMAIL PROTECTED]>, David Larkin <[EMAIL PROTECTED]> typed:
> >> Dragoncrest wrote:
> >> > I've got a rather odd question, but I'm looking for the easiest way to
> >> > determin how much ram I have on a given system without rebooting it.  I'm
> >> > sure that there is some kind of console command that tells me that info,
> >> > but I have no idea where to begin looking to find out.  Does anybody
> >> > know?  Thanks.
> >> use the command dmesg
> >It may no longer be available there. The dmesg at boot time is
> >preserved in /var/run/dmesg.boot. The information should be there,
> >even if it's gone from dmesg.
> thats is kinda of odd, is that with 5.0-release?
> any clues on why?

That's with any version of FreeBSD. And the kernel dmesg buffer is
only so big. As other messages come in, older ones get flushed. SO if
you've been up long enough, you can lose the original boot
messages. If you boot single user and work there before going
multiuser, you can lose them in /var/run/dmesg.boot, even.

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Determining Ram

2003-02-03 Thread Roman Neuhauser
# [EMAIL PROTECTED] / 2003-02-03 23:44:06 -0500:
> On Sun, 2 Feb 2003 20:02:30 -0600, Mike Meyer wrote:
> 
> >In <[EMAIL PROTECTED]>, David Larkin <[EMAIL PROTECTED]> typed:
> >> Dragoncrest wrote:
> >> > I've got a rather odd question, but I'm looking for the easiest way to
> >> > determin how much ram I have on a given system without rebooting it.  I'm
> >> > sure that there is some kind of console command that tells me that info,
> >> > but I have no idea where to begin looking to find out.  Does anybody
> >> > know?  Thanks.
> >> use the command dmesg
> >
> >It may no longer be available there. The dmesg at boot time is
> >preserved in /var/run/dmesg.boot. The information should be there,
> >even if it's gone from dmesg.
> 
> thats is kinda of odd, is that with 5.0-release?
> 
> any clues on why?

RELENG_4 does this, too. the system message buffer is not of
infinite length.

-- 
If you cc me or remove the list(s) completely I'll most likely ignore
your message.see http://www.eyrie.org./~eagle/faqs/questions.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Determining Ram

2003-02-03 Thread Doug Reynolds
On Sun, 2 Feb 2003 20:02:30 -0600, Mike Meyer wrote:

>In <[EMAIL PROTECTED]>, David Larkin <[EMAIL PROTECTED]> typed:
>> Dragoncrest wrote:
>> > I've got a rather odd question, but I'm looking for the easiest way to
>> > determin how much ram I have on a given system without rebooting it.  I'm
>> > sure that there is some kind of console command that tells me that info,
>> > but I have no idea where to begin looking to find out.  Does anybody
>> > know?  Thanks.
>> use the command dmesg
>
>It may no longer be available there. The dmesg at boot time is
>preserved in /var/run/dmesg.boot. The information should be there,
>even if it's gone from dmesg.

thats is kinda of odd, is that with 5.0-release?

any clues on why?



---
doug reynolds | the maverick | [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Determining Ram

2003-02-02 Thread Doug Hardie
On Sunday, Feb 2, 2003, at 18:39 US/Pacific, Dragoncrest wrote:


Cool.  That worked.  A little more info than I wanted to sort 
through, but now that I know about that, I now have more information 
to pick through later on should I need any of that information that 
Dmesg listed.
At 01:02 AM 2/3/03 +, David Larkin wrote:
Dragoncrest wrote:

> I've got a rather odd question, but I'm looking for the 
easiest way to
> determin how much ram I have on a given system without rebooting 
it.  I'm
> sure that there is some kind of console command that tells me that 
info,
> but I have no idea where to begin looking to find out.  Does anybody
> know?  Thanks.
>
use the command dmesg

If your machine has been running too long the boot info will no longer 
be available through dmesg.  However, it is retained in 
/var/run/dmesg.boot.  That will always show the boot messages from the 
previous boot.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message


Re: Determining Ram

2003-02-02 Thread Dragoncrest
Cool.  That worked.  A little more info than I wanted to sort 
through, but now that I know about that, I now have more information to 
pick through later on should I need any of that information that Dmesg listed.

Thanks, that solved this issue, and gave me a new tool I never 
knew about for later troubleshooting.  :D

At 01:02 AM 2/3/03 +, David Larkin wrote:
Dragoncrest wrote:

> I've got a rather odd question, but I'm looking for the easiest 
way to
> determin how much ram I have on a given system without rebooting it.  I'm
> sure that there is some kind of console command that tells me that info,
> but I have no idea where to begin looking to find out.  Does anybody
> know?  Thanks.
>

use the command dmesg

>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Determining Ram

2003-02-02 Thread Mike Meyer
In <[EMAIL PROTECTED]>, David Larkin <[EMAIL PROTECTED]> typed:
> Dragoncrest wrote:
> > I've got a rather odd question, but I'm looking for the easiest way to
> > determin how much ram I have on a given system without rebooting it.  I'm
> > sure that there is some kind of console command that tells me that info,
> > but I have no idea where to begin looking to find out.  Does anybody
> > know?  Thanks.
> use the command dmesg

It may no longer be available there. The dmesg at boot time is
preserved in /var/run/dmesg.boot. The information should be there,
even if it's gone from dmesg.

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Determining Ram

2003-02-02 Thread David Larkin
Dragoncrest wrote:

> I've got a rather odd question, but I'm looking for the easiest way to
> determin how much ram I have on a given system without rebooting it.  I'm
> sure that there is some kind of console command that tells me that info,
> but I have no idea where to begin looking to find out.  Does anybody
> know?  Thanks.
>

use the command dmesg

>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Determining Ram

2003-02-02 Thread JacobRhoden
On Monday 03 February 2003 10:35, Dragoncrest wrote:
> I've got a rather odd question, but I'm looking for the easiest way to
> determin how much ram I have on a given system without rebooting it.  I'm
> sure that there is some kind of console command that tells me that info,
> but I have no idea where to begin looking to find out.  Does anybody
> know?  Thanks.

you could use the 'top' command

Jacob RhodenPhone: +61 3 8344 6102
ITS DivisionEmail: [EMAIL PROTECTED]
Melbourne University   Mobile: +61 403 788 386

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message