<?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: is SUDO 100% root? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508821#M365576</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;Need&lt;BR /&gt;&lt;BR /&gt;name of account executing the sudo command&lt;BR /&gt;the command&lt;BR /&gt;the /etc/sudoers file</description>
    <pubDate>Tue, 06 Oct 2009 15:10:04 GMT</pubDate>
    <dc:creator>Michael Steele_2</dc:creator>
    <dc:date>2009-10-06T15:10:04Z</dc:date>
    <item>
      <title>is SUDO 100% root?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508820#M365575</link>
      <description>Here is the example: nickel script downloaded tar file. login as root to untar it with no problem, but sudo to root can't untar it. what is behind this, environment variable? or is sudo 100% of root?</description>
      <pubDate>Tue, 06 Oct 2009 15:08:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508820#M365575</guid>
      <dc:creator>John Guster</dc:creator>
      <dc:date>2009-10-06T15:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: is SUDO 100% root?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508821#M365576</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Need&lt;BR /&gt;&lt;BR /&gt;name of account executing the sudo command&lt;BR /&gt;the command&lt;BR /&gt;the /etc/sudoers file</description>
      <pubDate>Tue, 06 Oct 2009 15:10:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508821#M365576</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2009-10-06T15:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: is SUDO 100% root?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508822#M365577</link>
      <description>&amp;gt; sudo to root can't untar it&lt;BR /&gt; &lt;BR /&gt;Hummmm, was there some sort of error message like parity error on disk, or did tar core dump, or out of memory? Maybe a permission problem or possibly a sudo error message such as the wrong permission on config files and directories?&lt;BR /&gt; &lt;BR /&gt;sudo works exactly as defined by the sudoers file. A bit more information will help.</description>
      <pubDate>Tue, 06 Oct 2009 16:07:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508822#M365577</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2009-10-06T16:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: is SUDO 100% root?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508823#M365578</link>
      <description>By default, sudo makes a 100% change to the user identity of the session, but a minimal change to the environment.&lt;BR /&gt;&lt;BR /&gt;If you run "sudo -s" to get a root shell, you'll get the shell specified in your regular $SHELL environment variable, using the shell startup scripts in your regular $HOME.&lt;BR /&gt;&lt;BR /&gt;This is so that if you prefer a plain "# " root prompt and another sysadmin at your site wants a 160-character colourful prompt with username + hostname + load level + pathname + a blinking clock, you both can easily get what you want without interfering with each other's setups.&lt;BR /&gt;&lt;BR /&gt;If you want to get /sbin and /usr/sbin included to your PATH when using sudo, you have to either use "sudo -i" (or "sudo -H -s" with older versions of sudo) or make your regular session startup scripts detect when the shell is running them as root and make the necessary changes.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 06 Oct 2009 18:08:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508823#M365578</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-10-06T18:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: is SUDO 100% root?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508824#M365579</link>
      <description>the permission is "ALL" since this login account is for the system administrator. We had security patch installed, then some script has to be run as root, not through the root from sudo. The error message is "you have to be root to run", and whoami tells it is root.</description>
      <pubDate>Tue, 06 Oct 2009 18:46:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508824#M365579</guid>
      <dc:creator>John Guster</dc:creator>
      <dc:date>2009-10-06T18:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: is SUDO 100% root?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508825#M365580</link>
      <description>Hi John:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; The error message is "you have to be root to run", and whoami tells it is root.&lt;BR /&gt;&lt;BR /&gt;There is a big difference between what 'whoami' and 'who am i' return.&lt;BR /&gt;&lt;BR /&gt;The first form ('whoami') returns the effective user name.  The second form ('who am i') returns the original, initial login name.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 06 Oct 2009 19:01:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/is-sudo-100-root/m-p/4508825#M365580</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-10-06T19:01:33Z</dc:date>
    </item>
  </channel>
</rss>

