<?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: executing c prog. with bash script in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991524#M923949</link>
    <description>The other kinds of problems to look for: Does the C program run when stdin, stdout, and stdin are not terminal devices? Does the C program create some sort of lock file, semaphore, or shared memory segment to keep more than one copy of itself running?&lt;BR /&gt;</description>
    <pubDate>Sat, 07 Jun 2003 18:17:42 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2003-06-07T18:17:42Z</dc:date>
    <item>
      <title>executing c prog. with bash script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991521#M923946</link>
      <description>hi, everyone.&lt;BR /&gt;i wrote a bash script which works alot like "devil" - it is supposed to stay always "up" and search processes in the system.&lt;BR /&gt;if they arent up, it will execute them with nohup command.&lt;BR /&gt;so, what is the problem?&lt;BR /&gt;the scripts (written in bash) need to execute a csh based scripts which in turn, executes the c-program.&lt;BR /&gt;the whole process works fine, until after a few days, for some reason, the main bash script runs the csh script but the csh script cant execute the c program...&lt;BR /&gt;i know the csh scripts runs because i can see it log files running but i see no evidence that the c-prog ran.&lt;BR /&gt;i tryed to use rehash and clear the process memory table in the bash script, but it didnt work.&lt;BR /&gt;can anyone suggest any ideas?&lt;BR /&gt;&lt;BR /&gt;thanks... &lt;BR /&gt;Oren.</description>
      <pubDate>Sat, 07 Jun 2003 12:48:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991521#M923946</guid>
      <dc:creator>Oren_3</dc:creator>
      <dc:date>2003-06-07T12:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: executing c prog. with bash script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991522#M923947</link>
      <description>forgot to mention, i am using a hpux-11i system on a n class machine...</description>
      <pubDate>Sat, 07 Jun 2003 12:50:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991522#M923947</guid>
      <dc:creator>Oren_3</dc:creator>
      <dc:date>2003-06-07T12:50:47Z</dc:date>
    </item>
    <item>
      <title>Re: executing c prog. with bash script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991523#M923948</link>
      <description>This seems like an overly complex scheme; I would probably do all of this within a C program that has been properly daemonized and make any script calls via the c system() or popen() functions. In any event, I would certainly avoid the csh. However, the key to finding your problem is to echo $status to your logfile (the equivalent of $? is bash) IMMEDIATELY after the csh script invokes the C program. A non-zero value (if the C program follows normal conventions) will indicate an error and the convention is that that value is errno.&lt;BR /&gt;</description>
      <pubDate>Sat, 07 Jun 2003 18:03:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991523#M923948</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-06-07T18:03:24Z</dc:date>
    </item>
    <item>
      <title>Re: executing c prog. with bash script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991524#M923949</link>
      <description>The other kinds of problems to look for: Does the C program run when stdin, stdout, and stdin are not terminal devices? Does the C program create some sort of lock file, semaphore, or shared memory segment to keep more than one copy of itself running?&lt;BR /&gt;</description>
      <pubDate>Sat, 07 Jun 2003 18:17:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executing-c-prog-with-bash-script/m-p/2991524#M923949</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-06-07T18:17:42Z</dc:date>
    </item>
  </channel>
</rss>

