<?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: User login question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482803#M798907</link>
    <description>Craig:&lt;BR /&gt;&lt;BR /&gt;If I understand the need correctly, you want an account setup to which a user "logs-in" but in doing so can only execute a particular application.  There are two simple ways to do this:&lt;BR /&gt;&lt;BR /&gt;1) As the last entry in the $HOME/.profile, 'exec' your script or application.  To prevent "shelling" out during the processing of the .profile place the following trap at the profile's beginning:&lt;BR /&gt;&lt;BR /&gt;trap "" 1 2 3&lt;BR /&gt;# ...main profile&lt;BR /&gt;exec &lt;YOUR_APPLICATION_OR_SCRIPT&gt;&lt;/YOUR_APPLICATION_OR_SCRIPT&gt;# ...end of profile&lt;BR /&gt;&lt;BR /&gt;This method gives you the advantage of setting up whatever environmental variables you need or want.&lt;BR /&gt;&lt;BR /&gt;2) In lieu of the above technique, declare the application or script in the /etc/passwd file in place of the normal shell (the seventh, colon-delimited field).&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Mon, 15 Jan 2001 16:08:04 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2001-01-15T16:08:04Z</dc:date>
    <item>
      <title>User login question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482802#M798906</link>
      <description>SA's.&lt;BR /&gt;&lt;BR /&gt;I have an account that is a general account with a password.&lt;BR /&gt;I need to prevent logins to this account but also keep the password.  The software that will use the account needs access but no user access.&lt;BR /&gt;&lt;BR /&gt;Any suggestions on how to do this?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Craig A. Sharp&lt;BR /&gt;Unix Systems Administrator&lt;BR /&gt;Roush Industries, Inc.</description>
      <pubDate>Mon, 15 Jan 2001 15:51:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482802#M798906</guid>
      <dc:creator>Craig A. Sharp</dc:creator>
      <dc:date>2001-01-15T15:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: User login question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482803#M798907</link>
      <description>Craig:&lt;BR /&gt;&lt;BR /&gt;If I understand the need correctly, you want an account setup to which a user "logs-in" but in doing so can only execute a particular application.  There are two simple ways to do this:&lt;BR /&gt;&lt;BR /&gt;1) As the last entry in the $HOME/.profile, 'exec' your script or application.  To prevent "shelling" out during the processing of the .profile place the following trap at the profile's beginning:&lt;BR /&gt;&lt;BR /&gt;trap "" 1 2 3&lt;BR /&gt;# ...main profile&lt;BR /&gt;exec &lt;YOUR_APPLICATION_OR_SCRIPT&gt;&lt;/YOUR_APPLICATION_OR_SCRIPT&gt;# ...end of profile&lt;BR /&gt;&lt;BR /&gt;This method gives you the advantage of setting up whatever environmental variables you need or want.&lt;BR /&gt;&lt;BR /&gt;2) In lieu of the above technique, declare the application or script in the /etc/passwd file in place of the normal shell (the seventh, colon-delimited field).&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 15 Jan 2001 16:08:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482803#M798907</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-01-15T16:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: User login question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482804#M798908</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;Excellent reply,  I can use it elsewhere.&lt;BR /&gt;&lt;BR /&gt;What I need to do is disable any logins to the account but leave the account and password intact.&lt;BR /&gt;&lt;BR /&gt;Craig</description>
      <pubDate>Mon, 15 Jan 2001 16:10:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482804#M798908</guid>
      <dc:creator>Craig A. Sharp</dc:creator>
      <dc:date>2001-01-15T16:10:15Z</dc:date>
    </item>
    <item>
      <title>Re: User login question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482805#M798909</link>
      <description>Craig:&lt;BR /&gt;&lt;BR /&gt;OK, then replace the login shell in /etc/passwd (for the account in question) with "/usr/bin/false".&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 15 Jan 2001 16:19:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-login-question/m-p/2482805#M798909</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-01-15T16:19:36Z</dc:date>
    </item>
  </channel>
</rss>

