- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Dmesg out put
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
03-25-2003 04:18 AM
03-25-2003 04:18 AM
STOP_IT set. Calling set_timer from step_time
When run dmesg the last line shows the above message... Whats the meaning of it?
Also dmesg gives
process pid == 13483, command RUN_shb_h6 does not have memory
locking privileges required for using
large text pages in this system version. Either correct
the privileges (see setprivgrp(1m)) or chatr the executable
text to a non +L option see chatr(1m)
Any help?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2003 04:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2003 04:32 AM
03-25-2003 04:32 AM
Re: Dmesg out put
#getprivgrp
will show the existing privileges
#setprivgrp
MLOCK is the privilege for Memory locking.
Add the user who owns the PID 13483 to the group to which the MLOCK privilege was given.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2003 05:35 AM
03-25-2003 05:35 AM
Re: Dmesg out put
Thanks a lot Manigandan.... I think this should solve my problem. I am just testing this command on our test server and will apply it on production soon....Thanks a lot again....Are you from Tamil Nadu?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2003 07:03 AM
03-25-2003 07:03 AM
Re: Dmesg out put
Since the December 2001, patch set on 11.00 this ccommand has been needed to get oracle databases memory privilidges.
This can allso be accomplised by having the entries in the /etcprivgroup file noted above.
Also required for Software AG's Adabas.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com