<?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: Corrupted files in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961536#M814322</link>
    <description>'cksum' is a quick test of corruption when transporting files, say from one server to another via ftp, or when copying files between new and old file systems.&lt;BR /&gt;&lt;BR /&gt;'cksum' executes a hashing algorithm for the puspose of error correction and the results will be the same if a successful transport occurred.</description>
    <pubDate>Tue, 29 Apr 2003 14:47:17 GMT</pubDate>
    <dc:creator>Michael Steele_2</dc:creator>
    <dc:date>2003-04-29T14:47:17Z</dc:date>
    <item>
      <title>Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961527#M814313</link>
      <description>Hi&lt;BR /&gt;I have found some corrupted files on one filesystem. The files is ordinary text files. Is there any fast way to check if a file contains only printable characters.</description>
      <pubDate>Tue, 29 Apr 2003 10:10:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961527#M814313</guid>
      <dc:creator>Leif Halvarsson_2</dc:creator>
      <dc:date>2003-04-29T10:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961528#M814314</link>
      <description>How about:&lt;BR /&gt;# cat filename |vis&lt;BR /&gt;&lt;BR /&gt;vis will show garbage as \002 for example.</description>
      <pubDate>Tue, 29 Apr 2003 10:12:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961528#M814314</guid>
      <dc:creator>Cheryl Griffin</dc:creator>
      <dc:date>2003-04-29T10:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961529#M814315</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;# file *&lt;BR /&gt;&lt;BR /&gt;Robert-Jan.</description>
      <pubDate>Tue, 29 Apr 2003 10:13:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961529#M814315</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2003-04-29T10:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961530#M814316</link>
      <description>#file &lt;FILE-NAME&gt;&lt;/FILE-NAME&gt;</description>
      <pubDate>Tue, 29 Apr 2003 10:23:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961530#M814316</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2003-04-29T10:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961531#M814317</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;man file.&lt;BR /&gt;&lt;BR /&gt;to view the contents, strings filename.&lt;BR /&gt;&lt;BR /&gt;-balaji</description>
      <pubDate>Tue, 29 Apr 2003 10:27:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961531#M814317</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-04-29T10:27:15Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961532#M814318</link>
      <description>file file_name&lt;BR /&gt;&lt;BR /&gt;...will report ascii text or not.  ASCII text is printable characters.&lt;BR /&gt;&lt;BR /&gt;strings file_name |more&lt;BR /&gt;&lt;BR /&gt;...will allow you to convert binary to ascii text for reading purposes.</description>
      <pubDate>Tue, 29 Apr 2003 11:20:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961532#M814318</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-04-29T11:20:44Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961533#M814319</link>
      <description>Be carefull if you decide to use file from a script and check the output from the command for "ascii text" as the file command will attempt to try to find out what language an ascii file is written in (see man file).  This guess can often be wrong.  FOr instance, file believes that my /etc/hosts file is "s200 assembler program text".</description>
      <pubDate>Tue, 29 Apr 2003 11:54:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961533#M814319</guid>
      <dc:creator>Ian Lochray</dc:creator>
      <dc:date>2003-04-29T11:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961534#M814320</link>
      <description>As mentioned, the file command can be used to 'guess' what the contents might be. The problem is that unlike commercial operating systems, Unix does not maintain a concept of a file type. All ordinary files are simply a stream of bytes and only the creator knows what the file's content and purpose might be.&lt;BR /&gt;&lt;BR /&gt;As mentioned, the vis command can be used scan a file and if the output contains \0something, then there is at least one non-printable ASCII character.</description>
      <pubDate>Tue, 29 Apr 2003 13:45:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961534#M814320</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-04-29T13:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961535#M814321</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thank you everybody. vis show there is strange characters in som of the files. The problem seems to be with large files (&amp;gt;1MB). I think I first have to find out how the files have been corrupted.&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Apr 2003 14:29:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961535#M814321</guid>
      <dc:creator>Leif Halvarsson_2</dc:creator>
      <dc:date>2003-04-29T14:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted files</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961536#M814322</link>
      <description>'cksum' is a quick test of corruption when transporting files, say from one server to another via ftp, or when copying files between new and old file systems.&lt;BR /&gt;&lt;BR /&gt;'cksum' executes a hashing algorithm for the puspose of error correction and the results will be the same if a successful transport occurred.</description>
      <pubDate>Tue, 29 Apr 2003 14:47:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupted-files/m-p/2961536#M814322</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-04-29T14:47:17Z</dc:date>
    </item>
  </channel>
</rss>

