- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- memory dumb attack
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2001 09:12 PM
12-11-2001 09:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2001 09:21 PM
12-11-2001 09:21 PM
Re: memory dumb attack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2001 09:27 PM
12-11-2001 09:27 PM
SolutionThere are two ways to determine this:
1. Use dmesg(1M) to read the memory information from the kernel message
buffer:
Near the bottom of the output of dmesg should be something similar to
the following:
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 65536 Kbytes, lockable: 39496 Kbytes, available: 48264 Kbytes
The Physical: section gives you the total number of kilobytes of
physical ram.
Do not be alarmed if the memory information is not in the dmesg output.
The system error message buffer is of small, finite size. If the memory
information cannot be found there then go to step 2.
2. Use adb(1) to read the memory information from the running
kernel/memory:
[Remember the numbers returned must be multiplied by 4]
For 10.X execute:
echo "physmem /D" | adb /stand/vmunix /dev/kmem
This should return:
physmem:
physmem: 16384
For 11.X 32 bit execute:
echo "phys_mem_pages /D" | adb /stand/vmunix /dev/kmem
This should return:
phys_mem_pages:
phys_mem_pages: 106496
For 11.X 64 bit execute:
echo "phys_mem_pages/D" | adb64 -k /stand/vmunix /dev/mem
This should return:
phys_mem_pages:
phys_mem_pages: 523264
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2001 09:47 PM
12-11-2001 09:47 PM
Re: memory dumb attack
glance -> and "m" will do it!
I don't forget this one and hence is my first source for checking memory on the system.
HTH
raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2001 10:08 PM
12-11-2001 10:08 PM
Re: memory dumb attack
Another way to find out the physical memory is to run mstm information tool on it.
Within mstm, highlight "Memory", then from the menubar, select "Tools", "Information", followed by "Run".
Detailed information on your physical memory will be shown including:
1) Configurable memory
2) Page size of memory
3) Memory interleaving status
4) Memory board inventory
5) Memory error log summary (eg. single-bit errors)
6) Page Deallocation Table (PDT)
Hope this helps. Regards.
Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com