<?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/issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990830#M422181</link>
    <description>Hi,&lt;BR /&gt;when is the policy displayed, before or after the login prompt? We display ours after the login prompt via /etc/profile and the user has to confirm (Y/N). &lt;BR /&gt;Otherwise you may give too much information away, before the user has actually logged on. &lt;BR /&gt;&lt;BR /&gt;Bad example "You have acccessed &amp;lt; machine name&amp;gt; owned by &amp;lt; company &amp;gt;, supported by &amp;lt; contact details&amp;gt;"</description>
    <pubDate>Fri, 14 Jul 2006 04:07:39 GMT</pubDate>
    <dc:creator>Peter Godron</dc:creator>
    <dc:date>2006-07-14T04:07:39Z</dc:date>
    <item>
      <title>/etc/issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990827#M422178</link>
      <description>I am building a new server and will need to mimic the acceptable use policy that we have on our current Prod server.  The policy displays at login time.  I have found the /etc/issue file that contains the policy and put in on the new server.  I have also added the following to the inetd.conf: &lt;BR /&gt;&lt;BR /&gt;telnet       stream tcp nowait root /usr/lbin/telnetd  telnetd -b /etc/issue&lt;BR /&gt;&lt;BR /&gt;It is still not working.  Can someone tell me what I am missing please?&lt;BR /&gt;&lt;BR /&gt;Thank you</description>
      <pubDate>Thu, 13 Jul 2006 16:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990827#M422178</guid>
      <dc:creator>chmc</dc:creator>
      <dc:date>2006-07-13T16:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990828#M422179</link>
      <description>First do a "cat /etc/issue" to make sure that is contains your message.&lt;BR /&gt;&lt;BR /&gt;Next (and this is what I think you missed), issue an "inetd -c" command to send a SIGHUP to the inetd daemon to trigger a reread of the /etc/inetd.conf file.</description>
      <pubDate>Thu, 13 Jul 2006 17:10:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990828#M422179</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-07-13T17:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990829#M422180</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The entry in inetd.conf is fine and other solution provided to refresh inetd is 100% fine. Still You can check permissions on /etc/issue. But it should display banner for root atleast. &lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Fri, 14 Jul 2006 04:01:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990829#M422180</guid>
      <dc:creator>Harmanjit_1</dc:creator>
      <dc:date>2006-07-14T04:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990830#M422181</link>
      <description>Hi,&lt;BR /&gt;when is the policy displayed, before or after the login prompt? We display ours after the login prompt via /etc/profile and the user has to confirm (Y/N). &lt;BR /&gt;Otherwise you may give too much information away, before the user has actually logged on. &lt;BR /&gt;&lt;BR /&gt;Bad example "You have acccessed &amp;lt; machine name&amp;gt; owned by &amp;lt; company &amp;gt;, supported by &amp;lt; contact details&amp;gt;"</description>
      <pubDate>Fri, 14 Jul 2006 04:07:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990830#M422181</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-07-14T04:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990831#M422182</link>
      <description>Hi chmc,&lt;BR /&gt;&lt;BR /&gt;# inetd -c&lt;BR /&gt;-c   Reconfigure the Internet daemon; in other words, force the current inetd to reread /etc/inetd.conf.  This option sends   the signal SIGHUP to the Internet daemon that is currently running.  Any configuration errors that occur during the&lt;BR /&gt;reconfiguration are logged to the syslogd daemon facility.&lt;BR /&gt;&lt;BR /&gt;rgs,&lt;BR /&gt;&lt;BR /&gt;ran&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Jul 2006 05:33:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990831#M422182</guid>
      <dc:creator>rariasn</dc:creator>
      <dc:date>2006-07-14T05:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990832#M422183</link>
      <description>Thanks to all that replied.  The inetd -c was what I was missing.  Issue is resolved and I am on to the next one.</description>
      <pubDate>Fri, 14 Jul 2006 08:03:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-issue/m-p/4990832#M422183</guid>
      <dc:creator>chmc</dc:creator>
      <dc:date>2006-07-14T08:03:40Z</dc:date>
    </item>
  </channel>
</rss>

