HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cpumap startup script
Operating System - HP-UX
1832237
Members
23578
Online
110041
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
07-22-2002 02:44 PM
07-22-2002 02:44 PM
hi,
On V2600 system, the cpumap startup script takes a long time to complete.
<
Apparently this cstm command in the script takes up the time :
echo "selclass qualifier cpu\ninfo\nwait\ninfolog\n$cmd done\nexit\nOK\n" | /usr/sbin/cstm | /usr/bin/grep -v -e "Log creation time:" -
e "Updating Map" | /usr/bin/sed "/(Wait).*disabled/,/^$/d" > $TOMBSTONE_DIR/cpumap ;
I understand this is useful for tombstones info, during crashes. But,for normally scheduled reboots , is it advisable to disable this (say when we reboot the system twice for patches , kernel etc).?
Or is there any smart way to run this in the background even as it does the boot up process.
Has anybody around tweaked this fella? It seems faster on N servers.
thanks
-raj
Take it easy.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2002 10:54 PM
07-22-2002 10:54 PM
Solution
Hi
I Believe that it is loaded by the HAO
HAT-CLIENT software. The program copies processor information to the
/var/tombstones/cpumap file at reboot.
I understand that the /var/tombstones/cpumap file is no longer used and can be disabled .
The easiest solution is edit the
/etc/rc.config.d/cpumap file and CPUMAP=0.
Steve Steel
I Believe that it is loaded by the HAO
HAT-CLIENT software. The program copies processor information to the
/var/tombstones/cpumap file at reboot.
I understand that the /var/tombstones/cpumap file is no longer used and can be disabled .
The easiest solution is edit the
/etc/rc.config.d/cpumap file and CPUMAP=0.
Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP