<?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: /etc/shells? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024780#M131291</link>
    <description>&lt;A href="http://devrsrc1.external.hp.com/STKLI/man/11iv1.5/shells_4.html" target="_blank"&gt;http://devrsrc1.external.hp.com/STKLI/man/11iv1.5/shells_4.html&lt;/A&gt; - on hp.&lt;BR /&gt;&lt;BR /&gt;as to solaris see here:&lt;A href="http://docs.sun.com/db/doc/805-3480/6j3ahiigm?a=view" target="_blank"&gt;http://docs.sun.com/db/doc/805-3480/6j3ahiigm?a=view&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;in particular:'This file is not included in the standard release, so it must be added if users are to be allowed to use .forward files to forward mail to a program or to a file. It is possible to create the file by hand by using grep to identify all of the shells listed in your password file, then entering them manually in the file, but it is easier to use the procedure below, which employes a script that can be downloaded'&lt;BR /&gt;Just remembered because once (in previous unix life :)) used to mess with .forward.&lt;BR /&gt;&lt;BR /&gt;Zeev&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 15 Jul 2003 21:42:49 GMT</pubDate>
    <dc:creator>Zeev Schultz</dc:creator>
    <dc:date>2003-07-15T21:42:49Z</dc:date>
    <item>
      <title>/etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024777#M131288</link>
      <description>Can anybody please let me know where I can find the corresponding file of /etc/shells on Solaris servers?&lt;BR /&gt;&lt;BR /&gt;Thanks,</description>
      <pubDate>Tue, 15 Jul 2003 21:29:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024777#M131288</guid>
      <dc:creator>Hanry Zhou</dc:creator>
      <dc:date>2003-07-15T21:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024778#M131289</link>
      <description>Hi Hanry,&lt;BR /&gt;&lt;BR /&gt;I think its the same file but it might not created by default. You can just create the file manually or run the getusershell(3C) system call to get the list of supported shells. See the following Sun URL :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://access1.sun.com/technotes/01248.html" target="_blank"&gt;http://access1.sun.com/technotes/01248.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;James.</description>
      <pubDate>Tue, 15 Jul 2003 21:36:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024778#M131289</guid>
      <dc:creator>James Murtagh</dc:creator>
      <dc:date>2003-07-15T21:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024779#M131290</link>
      <description>Sun's convention is a little different. They have a library function called getusershell() that will list the standard shells. You can create your own /etc/shell and it will augment those listed by getusershell().&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Jul 2003 21:40:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024779#M131290</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-07-15T21:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024780#M131291</link>
      <description>&lt;A href="http://devrsrc1.external.hp.com/STKLI/man/11iv1.5/shells_4.html" target="_blank"&gt;http://devrsrc1.external.hp.com/STKLI/man/11iv1.5/shells_4.html&lt;/A&gt; - on hp.&lt;BR /&gt;&lt;BR /&gt;as to solaris see here:&lt;A href="http://docs.sun.com/db/doc/805-3480/6j3ahiigm?a=view" target="_blank"&gt;http://docs.sun.com/db/doc/805-3480/6j3ahiigm?a=view&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;in particular:'This file is not included in the standard release, so it must be added if users are to be allowed to use .forward files to forward mail to a program or to a file. It is possible to create the file by hand by using grep to identify all of the shells listed in your password file, then entering them manually in the file, but it is easier to use the procedure below, which employes a script that can be downloaded'&lt;BR /&gt;Just remembered because once (in previous unix life :)) used to mess with .forward.&lt;BR /&gt;&lt;BR /&gt;Zeev&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Jul 2003 21:42:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024780#M131291</guid>
      <dc:creator>Zeev Schultz</dc:creator>
      <dc:date>2003-07-15T21:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024781#M131292</link>
      <description>Hi Hanry,&lt;BR /&gt;&lt;BR /&gt;The /etc/shells in Solaris is located in same directory of HPUX. If the file didn??t exist its necessary create...&lt;BR /&gt;Any problems with ftp???&lt;BR /&gt;&lt;BR /&gt;Look at this link: &lt;A href="http://docs.sun.com/?q=%2Fetc%2Fshells" target="_blank"&gt;http://docs.sun.com/?q=%2Fetc%2Fshells&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Good Luck.&lt;BR /&gt;&lt;BR /&gt;Valkiria&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Jul 2003 13:47:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024781#M131292</guid>
      <dc:creator>Valkiria Santos</dc:creator>
      <dc:date>2003-07-16T13:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024782#M131293</link>
      <description>Ok,&lt;BR /&gt;&lt;BR /&gt;thanks for messages,&lt;BR /&gt;Now it comes to my stupid questions, why do I need /etc/shells? seems the system is working ok without it?</description>
      <pubDate>Thu, 17 Jul 2003 18:19:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024782#M131293</guid>
      <dc:creator>Hanry Zhou</dc:creator>
      <dc:date>2003-07-17T18:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024783#M131294</link>
      <description>With so many shells cropping up everywhere, this is a control a sysadmin has on the users shells, so you can define what are the shells that are authorized to be run in a server.</description>
      <pubDate>Thu, 17 Jul 2003 18:31:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024783#M131294</guid>
      <dc:creator>Vasikaran Venkatesan</dc:creator>
      <dc:date>2003-07-17T18:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/shells?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024784#M131295</link>
      <description>man getusershell&lt;BR /&gt;&lt;BR /&gt;DESCRIPTION&lt;BR /&gt;     The getusershell() function returns a  pointer  to  a  legal&lt;BR /&gt;     user  shell  as  defined  by  the system manager in the file&lt;BR /&gt;     /etc/shells. IF /etc/shells DOES NOT EXIST,  the  following   &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;Note&lt;BR /&gt;     locations  of  the  standard  system  shells are used in its&lt;BR /&gt;     place:&lt;BR /&gt;     /usr/bin/sh                   /usr/bin/csh&lt;BR /&gt;     /usr/bin/ksh                  /usr/bin/jsh&lt;BR /&gt;     /bin/sh                       /bin/csh&lt;BR /&gt;     /bin/ksh                      /bin/jsh&lt;BR /&gt;     /sbin/sh    &lt;BR /&gt;&lt;BR /&gt;The idea is to give a greater degree of control over who can use ftp -&lt;BR /&gt;for example it's possible to turn off access completely just by creating&lt;BR /&gt;an empty /etc/shells&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jul 2003 19:37:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-shells/m-p/3024784#M131295</guid>
      <dc:creator>Paul Sperry</dc:creator>
      <dc:date>2003-07-17T19:37:19Z</dc:date>
    </item>
  </channel>
</rss>

