<?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: command problem in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959241#M77017</link>
    <description>1. snipped from the open man page.&lt;BR /&gt;&lt;BR /&gt;       The  open()  system  call  is  used  to  convert a pathname into a file&lt;BR /&gt;       descriptor (a small, non-negative integer for use in subsequent I/O  as&lt;BR /&gt;       with  read,  write,  etc.).   When  the  call  is  successful, the file&lt;BR /&gt;       descriptor returned will be the lowest file  descriptor  not  currently&lt;BR /&gt;       open  for  the  process.  This call creates a new open file, not shared&lt;BR /&gt;       with any other process.  (But shared  open  files  may  arise  via  the&lt;BR /&gt;       fork(2)  system  call.)   The new file descriptor is set to remain open&lt;BR /&gt;       across exec functions (see fcntl(2)).  The file offset is  set  to  the&lt;BR /&gt;       beginning of the file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2. man bash and search for ulimit. it controls resources available for a shell and process started from it.&lt;BR /&gt;&lt;BR /&gt;3. no idea. &lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;-balaji</description>
    <pubDate>Fri, 25 Apr 2003 06:30:37 GMT</pubDate>
    <dc:creator>Balaji N</dc:creator>
    <dc:date>2003-04-25T06:30:37Z</dc:date>
    <item>
      <title>command problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959240#M77016</link>
      <description>1. what's file descriptor?&lt;BR /&gt;&lt;BR /&gt;2. how can i ensure that a command use only a certain amount of resources when it is excuted?&lt;BR /&gt;&lt;BR /&gt;3.how to check the file contain unprintable characters?&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Apr 2003 05:51:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959240#M77016</guid>
      <dc:creator>neocosmic</dc:creator>
      <dc:date>2003-04-25T05:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: command problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959241#M77017</link>
      <description>1. snipped from the open man page.&lt;BR /&gt;&lt;BR /&gt;       The  open()  system  call  is  used  to  convert a pathname into a file&lt;BR /&gt;       descriptor (a small, non-negative integer for use in subsequent I/O  as&lt;BR /&gt;       with  read,  write,  etc.).   When  the  call  is  successful, the file&lt;BR /&gt;       descriptor returned will be the lowest file  descriptor  not  currently&lt;BR /&gt;       open  for  the  process.  This call creates a new open file, not shared&lt;BR /&gt;       with any other process.  (But shared  open  files  may  arise  via  the&lt;BR /&gt;       fork(2)  system  call.)   The new file descriptor is set to remain open&lt;BR /&gt;       across exec functions (see fcntl(2)).  The file offset is  set  to  the&lt;BR /&gt;       beginning of the file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2. man bash and search for ulimit. it controls resources available for a shell and process started from it.&lt;BR /&gt;&lt;BR /&gt;3. no idea. &lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;-balaji</description>
      <pubDate>Fri, 25 Apr 2003 06:30:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959241#M77017</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-04-25T06:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: command problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959242#M77018</link>
      <description>Thanks balaji for answering 1. and 2. I was wondering how best to answer these unix theory questions.&lt;BR /&gt;&lt;BR /&gt;for 3.)&lt;BR /&gt;&lt;BR /&gt;# file &lt;FILENAME&gt; should give you some details&lt;BR /&gt;&lt;BR /&gt;# strings &lt;FILENAME&gt; may be used.&lt;BR /&gt;&lt;BR /&gt;FWIW.&lt;BR /&gt;&lt;BR /&gt;- ramd.&lt;/FILENAME&gt;&lt;/FILENAME&gt;</description>
      <pubDate>Fri, 25 Apr 2003 06:44:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959242#M77018</guid>
      <dc:creator>Ramkumar Devanathan</dc:creator>
      <dc:date>2003-04-25T06:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: command problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959243#M77019</link>
      <description>u r welcome ram.&lt;BR /&gt;&lt;BR /&gt;and fyi, strings prints only printable characters in a file. noway u can know of non-printable chars.&lt;BR /&gt;&lt;BR /&gt;-balaji</description>
      <pubDate>Fri, 25 Apr 2003 07:17:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959243#M77019</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-04-25T07:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: command problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959244#M77020</link>
      <description>Neocosmic,&lt;BR /&gt;&lt;BR /&gt;Yup, balaji's right. that's why i'd mentioned the word 'use'...&lt;BR /&gt;&lt;BR /&gt;- ramd.</description>
      <pubDate>Fri, 25 Apr 2003 07:43:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959244#M77020</guid>
      <dc:creator>Ramkumar Devanathan</dc:creator>
      <dc:date>2003-04-25T07:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: command problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959245#M77021</link>
      <description>To check for unprintable characters you could try&lt;BR /&gt;&lt;BR /&gt;cat &lt;FILENAME&gt; -v &amp;gt; &lt;NEWFILE&gt;&lt;BR /&gt;&lt;BR /&gt;Then you can search the newfile for funny looking things like ^Z&lt;BR /&gt;&lt;BR /&gt;hth,&lt;BR /&gt;&lt;BR /&gt;clay&lt;/NEWFILE&gt;&lt;/FILENAME&gt;</description>
      <pubDate>Sat, 26 Apr 2003 09:52:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/command-problem/m-p/2959245#M77021</guid>
      <dc:creator>Clay Davidson</dc:creator>
      <dc:date>2003-04-26T09:52:32Z</dc:date>
    </item>
  </channel>
</rss>

