HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dmesg and /dev/kmem
Operating System - HP-UX
1827697
Members
3109
Online
109967
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
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
06-12-2001 11:03 AM
06-12-2001 11:03 AM
dmesg and /dev/kmem
We are running HP-UX 11.0 on 9000 class machines.
What should the permissions be for dmesg and /dev/kmem ? dmesg only works for user root because /dev/kmem is not readable for everyone. Some casual users need to run dmesg to get the Physical memory info.
(We do not have dmesg dumping to /var/adm/messages.)
Solaris has 3555 permissions on for dmesg and 640 for kmem. I checked a HP 9000 server in another admin group we have and they had /dev/kmem set at 644 and dmesg at 555 which allows dmesg to work for common users.
Here is what I have:
crw-r----- 1 bin sys 3 0x000001 Jan 19 2000 /dev/kmem
-r-xr-xr-x 1 bin bin 155648 Nov 7 1997 /sbin/dmesg
What should the permissions be for dmesg and /dev/kmem ? dmesg only works for user root because /dev/kmem is not readable for everyone. Some casual users need to run dmesg to get the Physical memory info.
(We do not have dmesg dumping to /var/adm/messages.)
Solaris has 3555 permissions on for dmesg and 640 for kmem. I checked a HP 9000 server in another admin group we have and they had /dev/kmem set at 644 and dmesg at 555 which allows dmesg to work for common users.
Here is what I have:
crw-r----- 1 bin sys 3 0x000001 Jan 19 2000 /dev/kmem
-r-xr-xr-x 1 bin bin 155648 Nov 7 1997 /sbin/dmesg
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2001 11:11 AM
06-12-2001 11:11 AM
Re: dmesg and /dev/kmem
I would set /dev/mem and /dev/kmem to 644 but make sure that it is owned by root. 555 for dmesg and again owned by root.
Clay
Clay
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2001 11:12 AM
06-12-2001 11:12 AM
Re: dmesg and /dev/kmem
Hi again,
Be awrare that dmesg will not always display memory; dmesh uses a circular buffer and once that is overwritten; the initial data is gone.
Be awrare that dmesg will not always display memory; dmesh uses a circular buffer and once that is overwritten; the initial data is gone.
If it ain't broke, I can fix that.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP