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
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
06-29-2000 12:40 PM
06-29-2000 12:40 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2000 04:03 PM
06-29-2000 04:03 PM
Re: SYSDEF
Do you mean the returned values are incorrect when compared to what shows up in SAM? Or do you mean it is possible to set values outside of SAM taht SAM considers invalid, and sysdef will show them?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2000 05:32 PM
06-29-2000 05:32 PM
SolutionAny particular parameters? If you do a sysdef and the UNITS column for the parm says Pages, get the page size from dmesg (default 4096) and multiply that by the parameters value. You should see that the sysdef and the SAM value will match.
For example, sysdef shows maxdsiz=16384 and UNITS=Pages. 16384*4096=67108864. The same value is seen in SAM.
I hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2000 05:38 PM
06-29-2000 05:38 PM
Re: SYSDEF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2000 11:42 PM
06-29-2000 11:42 PM
Re: SYSDEF
I hate to say it, but I believe sam. sysdef is 'ok' at best. It doesn't list half the useful parameters anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 02:48 AM
06-30-2000 02:48 AM
Re: SYSDEF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 03:04 AM
06-30-2000 03:04 AM
Re: SYSDEF
For example, if you have bufpages set equal to zero in the kernel configuration file, this, you will notice has changed to a higher value due to the dynamic nature of paging and cacheing.
The value of netmemmax can be deduced or confirmed from syslog file as different from what the kernel configuration showed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 10:50 AM
06-30-2000 10:50 AM
Re: SYSDEF
Denver - What you have said makes a lot of sense! And as Chris pointed out, some of the variables would be dynamic.
Neil - Good point, but only a few values are listed.
Sorry I didn't explain myself better in the first place! What I was trying to achieve was to get a report that would show the actual setting that were entered in SAM.
Thanks to everyone for your responses!