<?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: admin tool in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503154#M216921</link>
    <description>CVS tools also comes to mind but it won't add comments into the edited file. It will follow up the changes separately. We use CVS to update our DNS database for obvious reasons as well as our user database. &lt;BR /&gt;&lt;BR /&gt;On the ultimate end, CVS can easily be circumvented by putting gibberish in the explanations. Best way is the user willing to update while modifying critical files.</description>
    <pubDate>Fri, 11 Mar 2005 14:36:19 GMT</pubDate>
    <dc:creator>Mel Burslan</dc:creator>
    <dc:date>2005-03-11T14:36:19Z</dc:date>
    <item>
      <title>admin tool</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503152#M216919</link>
      <description>Anyone know of a tool that puts comment information into system files as they are edited - as in if you modify the /etc/hosts file, it would put date/time and initials on the entry? Thanks...</description>
      <pubDate>Fri, 11 Mar 2005 14:22:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503152#M216919</guid>
      <dc:creator>Michael Murphy_2</dc:creator>
      <dc:date>2005-03-11T14:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: admin tool</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503153#M216920</link>
      <description>Yep, it's called vi and your fingers.  If you modify it, you put comments in as to when and why.&lt;BR /&gt;&lt;BR /&gt;Other than, I know of nothing that does this.</description>
      <pubDate>Fri, 11 Mar 2005 14:33:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503153#M216920</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-03-11T14:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: admin tool</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503154#M216921</link>
      <description>CVS tools also comes to mind but it won't add comments into the edited file. It will follow up the changes separately. We use CVS to update our DNS database for obvious reasons as well as our user database. &lt;BR /&gt;&lt;BR /&gt;On the ultimate end, CVS can easily be circumvented by putting gibberish in the explanations. Best way is the user willing to update while modifying critical files.</description>
      <pubDate>Fri, 11 Mar 2005 14:36:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503154#M216921</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-03-11T14:36:19Z</dc:date>
    </item>
    <item>
      <title>Re: admin tool</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503155#M216922</link>
      <description>You can incorporate RCS into the editing tool you use (e.g., vi)&lt;BR /&gt;&lt;BR /&gt;Example, vi-wrapper script that checks to see if a file is under RCS control. If so, use RCS to do the checkout (co) and checkin (ci). If the file is not under RCS control then will invoke vi normally.&lt;BR /&gt;&lt;BR /&gt;Using the RCS tool will allow you to input comments for each edit (why the edit was done and who did the edit). The date will be stored with each edit.&lt;BR /&gt;&lt;BR /&gt;Attached is the vi-wrapper script&lt;BR /&gt;&lt;BR /&gt;NOTE: It is up to the user to put in the comments. The date entry will be automatic but as to who and why, this will need user input.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Mar 2005 14:39:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503155#M216922</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-03-11T14:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: admin tool</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503156#M216923</link>
      <description>IBM's "Rational Clearcase" is probably a solution.  It's a commercial product.  I haven't used them recently, but at one time the Rational tool suite seemed pretty good.&lt;BR /&gt;&lt;BR /&gt;AFAIK, the above solutions are all manual (haven't used CVS, assume it's manual like RCS)--people who edit the files have to agree to comply.  I believe, but am not sure, that Clearcase's versioning takes place outside user control (it used to be a modification to the filesystem itself).  I think versioning can probably be set up to take place always.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www-306.ibm.com/software/awdtools/clearcase/features/index.html" target="_blank"&gt;http://www-306.ibm.com/software/awdtools/clearcase/features/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www3.software.ibm.com/ibmdl/pub/software/rational/web/datasheets/version6/clearcase.pdf" target="_blank"&gt;http://www3.software.ibm.com/ibmdl/pub/software/rational/web/datasheets/version6/clearcase.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Mic</description>
      <pubDate>Fri, 11 Mar 2005 18:21:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/admin-tool/m-p/3503156#M216923</guid>
      <dc:creator>Mic V.</dc:creator>
      <dc:date>2005-03-11T18:21:41Z</dc:date>
    </item>
  </channel>
</rss>

