HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: su_group
Operating System - Linux
1830250
Members
2635
Online
110000
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
11-02-2006 09:31 PM
11-02-2006 09:31 PM
I can't run su_group command on linux clients, but can in Solaris. The command path exists but gives errors: 'permission denied' or 'cannot open perl script'. Thanks.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2006 09:57 PM
11-02-2006 09:57 PM
Solution
This is not a standard command on any Linux distribution I know.
The "cannot open perl script" might suggest that the su_group command is actually implemented as a script. Check the permissions of the command file: for scripts, the "execute" permission alone is not enough. The user running the script needs the "read" permission too.
You can also use the "file" command to identify the file type: if "file /whatever/path/su_group" has a word "text" in its output, you can be sure the su_group is actually a script.
You'll need to check the pathname of the command interpreter the script uses. It's normally specified on the first line of the script, and it should look like this:
#!/some/script/interpreter
If the script does not have this kind of line, it is normally executed using /bin/sh.
When you know the name of the interpreter, check the permissions of the interpreter file. If the interpreter does not exist at the specified path or has incorrect permissions, this may cause the error messages you're seeing.
The name "su_group" seems to suggest that the command might be designed to change the user's identity somehow. To do that, it needs root privileges... and in Linux, the suid bit *will not* take effect on scripts. Scripts with a suid bit are generally considered a bad idea: please avoid them. But if you must, the workaround could be a special perl interpreter named "suidperl". It is an optional component of a perl installation: read the documentation carefully before using it.
The "cannot open perl script" might suggest that the su_group command is actually implemented as a script. Check the permissions of the command file: for scripts, the "execute" permission alone is not enough. The user running the script needs the "read" permission too.
You can also use the "file" command to identify the file type: if "file /whatever/path/su_group" has a word "text" in its output, you can be sure the su_group is actually a script.
You'll need to check the pathname of the command interpreter the script uses. It's normally specified on the first line of the script, and it should look like this:
#!/some/script/interpreter
If the script does not have this kind of line, it is normally executed using /bin/sh.
When you know the name of the interpreter, check the permissions of the interpreter file. If the interpreter does not exist at the specified path or has incorrect permissions, this may cause the error messages you're seeing.
The name "su_group" seems to suggest that the command might be designed to change the user's identity somehow. To do that, it needs root privileges... and in Linux, the suid bit *will not* take effect on scripts. Scripts with a suid bit are generally considered a bad idea: please avoid them. But if you must, the workaround could be a special perl interpreter named "suidperl". It is an optional component of a perl installation: read the documentation carefully before using it.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2006 10:57 PM
11-02-2006 10:57 PM
Re: su_group
Matti, Thanks for your prompt response to this mail, appreciate. I'll check the script/command again and look out for any irregularities etc, thks.
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