<?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: Sam templates in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665271#M49376</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There is another option if you have&lt;BR /&gt;a script that generates the users/&lt;BR /&gt;passwords. You could set up sudo and&lt;BR /&gt;allow the user to run this task.&lt;BR /&gt;&lt;BR /&gt;-Michael</description>
    <pubDate>Thu, 14 Feb 2002 22:55:18 GMT</pubDate>
    <dc:creator>Michael Tully</dc:creator>
    <dc:date>2002-02-14T22:55:18Z</dc:date>
    <item>
      <title>Sam templates</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665270#M49375</link>
      <description>Sam templates and restricted Sam would seem to be the ideal way for me to allow a user to do all the account creation on a particular server.  Unfortunately the create user template insists on appending the user name to the home directory setting.  We use a generic home directory that is the same for every user.  The application handles the data so I don't want several thousand home directories when one will do.  I suppose worst case I could modify the /etc/skel/.profile and let sam create all those directories.  But all the .profile needs to do is start the app.  Maybe I'm being overly prissy, but it just seems inelegant.  I want to make this easy for the user, so all they have to do is type in the user name and password, yet I don't want to give them any more access than absolutely necessary.  Anyone know how to force Sam into behaving?</description>
      <pubDate>Thu, 14 Feb 2002 21:44:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665270#M49375</guid>
      <dc:creator>Terrence</dc:creator>
      <dc:date>2002-02-14T21:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: Sam templates</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665271#M49376</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There is another option if you have&lt;BR /&gt;a script that generates the users/&lt;BR /&gt;passwords. You could set up sudo and&lt;BR /&gt;allow the user to run this task.&lt;BR /&gt;&lt;BR /&gt;-Michael</description>
      <pubDate>Thu, 14 Feb 2002 22:55:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665271#M49376</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-02-14T22:55:18Z</dc:date>
    </item>
    <item>
      <title>Re: Sam templates</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665272#M49377</link>
      <description>Sudo is definitely a possibilty, and I do have scripts doing this for other servers.  This just seemed to be an easier cleaner way to have such a routine task performed with a minimal chance for screw ups.</description>
      <pubDate>Fri, 15 Feb 2002 16:43:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sam-templates/m-p/2665272#M49377</guid>
      <dc:creator>Terrence</dc:creator>
      <dc:date>2002-02-15T16:43:27Z</dc:date>
    </item>
  </channel>
</rss>

