<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: su_group in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891889#M25857</link>
    <description>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.</description>
    <pubDate>Fri, 03 Nov 2006 06:57:14 GMT</pubDate>
    <dc:creator>B.O</dc:creator>
    <dc:date>2006-11-03T06:57:14Z</dc:date>
    <item>
      <title>su_group</title>
      <link>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891887#M25855</link>
      <description>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.</description>
      <pubDate>Fri, 03 Nov 2006 05:31:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891887#M25855</guid>
      <dc:creator>B.O</dc:creator>
      <dc:date>2006-11-03T05:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: su_group</title>
      <link>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891888#M25856</link>
      <description>This is not a standard command on any Linux distribution I know.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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:&lt;BR /&gt;#!/some/script/interpreter&lt;BR /&gt;&lt;BR /&gt;If the script does not have this kind of line, it is normally executed using /bin/sh.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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.</description>
      <pubDate>Fri, 03 Nov 2006 05:57:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891888#M25856</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2006-11-03T05:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: su_group</title>
      <link>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891889#M25857</link>
      <description>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.</description>
      <pubDate>Fri, 03 Nov 2006 06:57:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/su-group/m-p/3891889#M25857</guid>
      <dc:creator>B.O</dc:creator>
      <dc:date>2006-11-03T06:57:14Z</dc:date>
    </item>
  </channel>
</rss>

