HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- sam - preventing insf on disks
Operating System - HP-UX
1831162
Members
3087
Online
110021
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
02-07-2005 09:01 AM
02-07-2005 09:01 AM
Can SAM be customized to prevent running INSF command on disks ?
There are non-root own'ed special devices, that get changed when SAM starts up.
Also, see the directory:
in directory: /usr/sam/lib, there is a sub-directory called: "pd". there is various INSF calls from these scripts.
pd/pd.tm: execute "cd /dev ; /sbin/insf -H %$PD_DEV_OBJ_HW_PATH% -e"
There are non-root own'ed special devices, that get changed when SAM starts up.
Also, see the directory:
in directory: /usr/sam/lib, there is a sub-directory called: "pd". there is various INSF calls from these scripts.
pd/pd.tm: execute "cd /dev ; /sbin/insf -H %$PD_DEV_OBJ_HW_PATH% -e"
Golf is a Good Walk Spoiled, Mark Twain.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2005 06:48 PM
02-07-2005 06:48 PM
Solution
Tom,
Rather than mess with SAM, why not use the mknod command to create duplicates of the device files with unique names that are owned by your non-root user. As long as they don't follow the standard device naming conventions insf should leave them alone...
HTH
Duncan
I am an HPE Employee
Rather than mess with SAM, why not use the mknod command to create duplicates of the device files with unique names that are owned by your non-root user. As long as they don't follow the standard device naming conventions insf should leave them alone...
HTH
Duncan
I am an HPE Employee

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