<?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: vi editor in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671175#M916136</link>
    <description>install vim. it still allows concurrent sessions, but it at least has the benefit of displaying a warning message if you are editing a file while another vim session has it open as well.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;mark</description>
    <pubDate>Mon, 25 Feb 2002 17:51:03 GMT</pubDate>
    <dc:creator>Mark Greene_1</dc:creator>
    <dc:date>2002-02-25T17:51:03Z</dc:date>
    <item>
      <title>vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671172#M916133</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I want to restrict multiple administrators simelteneously  edit a single file. Is there any way I can do it in vi?  My main concern  is multiple (including remote) admins try to umdate DNS hosts file. I want this file to be open by only one  admin at a give point of time.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Feb 2002 17:36:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671172#M916133</guid>
      <dc:creator>Rushank</dc:creator>
      <dc:date>2002-02-25T17:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671173#M916134</link>
      <description>I don't know of anything of hand, I assume you are looking for something to perform like vipw where the file is locked when someone is editing it.  You may have to write your own binary. You may try to get your hand on the vipw source code to see what they've done.&lt;BR /&gt;&lt;BR /&gt;GL,&lt;BR /&gt;C</description>
      <pubDate>Mon, 25 Feb 2002 17:43:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671173#M916134</guid>
      <dc:creator>Craig Rants</dc:creator>
      <dc:date>2002-02-25T17:43:12Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671174#M916135</link>
      <description>A baseball bat is your only option. Or you could use SCCS to control revision changes, which is something I've used in the past.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Mon, 25 Feb 2002 17:43:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671174#M916135</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-02-25T17:43:44Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671175#M916136</link>
      <description>install vim. it still allows concurrent sessions, but it at least has the benefit of displaying a warning message if you are editing a file while another vim session has it open as well.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;mark</description>
      <pubDate>Mon, 25 Feb 2002 17:51:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671175#M916136</guid>
      <dc:creator>Mark Greene_1</dc:creator>
      <dc:date>2002-02-25T17:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671176#M916137</link>
      <description>Didn't think about Harry's option, that could be a possibility. We have some sort of revision control software here, where you have to check a script/file out edit it, then check it back in... What a pain, obviously I almost never use it which defeats the point of having it...&lt;BR /&gt;&lt;BR /&gt;C</description>
      <pubDate>Mon, 25 Feb 2002 18:04:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671176#M916137</guid>
      <dc:creator>Craig Rants</dc:creator>
      <dc:date>2002-02-25T18:04:33Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671177#M916138</link>
      <description>Thanks ... For now vim looks like better option.!&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Feb 2002 18:08:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671177#M916138</guid>
      <dc:creator>Rushank</dc:creator>
      <dc:date>2002-02-25T18:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671178#M916139</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The other way is to write a wrapper script for vi (below is a simplistic script which assumes only one parameter and it can be enhanced to your needs) eg.&lt;BR /&gt;&lt;BR /&gt;# mv /usr/bin/vi /usr/bin/vi.bin&lt;BR /&gt;# vi /usr/bin/vi&lt;BR /&gt;&lt;BR /&gt;#!/sbin/sh&lt;BR /&gt;if [ -e /tmp/$1.vilck ]&lt;BR /&gt;then&lt;BR /&gt;  echo "Someone is currently editing $1. Please try again later..."&lt;BR /&gt;  exit 1&lt;BR /&gt;else&lt;BR /&gt;  touch /tmp/$1.vilck&lt;BR /&gt;  /usr/bin/vi.bin $1&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Tue, 26 Feb 2002 01:00:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671178#M916139</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-02-26T01:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: vi editor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671179#M916140</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I forgot to remove the lock "semaphore" upon exit. Revised as follows:&lt;BR /&gt;&lt;BR /&gt;#!/sbin/sh &lt;BR /&gt;if [ -e /tmp/$1.vilck ] &lt;BR /&gt;then &lt;BR /&gt;echo "Someone is currently editing $1. Please try again later..." &lt;BR /&gt;exit 1 &lt;BR /&gt;else &lt;BR /&gt;touch /tmp/$1.vilck &lt;BR /&gt;/usr/bin/vi.bin $1 &lt;BR /&gt;rm -f /tmp/$1.vilck&lt;BR /&gt;fi &lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Tue, 26 Feb 2002 01:02:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vi-editor/m-p/2671179#M916140</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-02-26T01:02:11Z</dc:date>
    </item>
  </channel>
</rss>

