<?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: which scripts are called by a particular script in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634077#M41953</link>
    <description>&lt;BR /&gt;Ther is no way to find that out without running the script in a way.&lt;BR /&gt;You could do the following:&lt;BR /&gt;Copy the script into an empty directory.&lt;BR /&gt;verify that PATH is not set in the script.&lt;BR /&gt;set PATH=.:/usr/bin:/... (not including the directories where the reall scripts are expected).&lt;BR /&gt;run the script (ksh scriptname). ksh will complain about he first command it does not find and exit. &lt;BR /&gt;You can provide a dummy version of the missing command in your working directory, or create a soft link to the real command, and the  repeat the procedure to find the second missing command. ETC. &lt;BR /&gt;&lt;BR /&gt;There is a tool tusc or truss, which allows you to track all system calls (you are interested in exec). &lt;BR /&gt;&lt;BR /&gt;Regards, Klaus&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 20 Dec 2001 16:21:41 GMT</pubDate>
    <dc:creator>Klaus Crusius</dc:creator>
    <dc:date>2001-12-20T16:21:41Z</dc:date>
    <item>
      <title>which scripts are called by a particular script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634076#M41952</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;How to find out which scripts are called by a particular script ???&lt;BR /&gt;Scripts are 2 big 2 examine by hand.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Guido</description>
      <pubDate>Thu, 20 Dec 2001 16:10:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634076#M41952</guid>
      <dc:creator>Guido Peerboom</dc:creator>
      <dc:date>2001-12-20T16:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: which scripts are called by a particular script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634077#M41953</link>
      <description>&lt;BR /&gt;Ther is no way to find that out without running the script in a way.&lt;BR /&gt;You could do the following:&lt;BR /&gt;Copy the script into an empty directory.&lt;BR /&gt;verify that PATH is not set in the script.&lt;BR /&gt;set PATH=.:/usr/bin:/... (not including the directories where the reall scripts are expected).&lt;BR /&gt;run the script (ksh scriptname). ksh will complain about he first command it does not find and exit. &lt;BR /&gt;You can provide a dummy version of the missing command in your working directory, or create a soft link to the real command, and the  repeat the procedure to find the second missing command. ETC. &lt;BR /&gt;&lt;BR /&gt;There is a tool tusc or truss, which allows you to track all system calls (you are interested in exec). &lt;BR /&gt;&lt;BR /&gt;Regards, Klaus&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Dec 2001 16:21:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634077#M41953</guid>
      <dc:creator>Klaus Crusius</dc:creator>
      <dc:date>2001-12-20T16:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: which scripts are called by a particular script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634078#M41954</link>
      <description>I would suggest that you place at the beginning of the script a set -x.  This shows what is executing as it executes.  You can probably key off the external programs being called by the path to them being shown.&lt;BR /&gt;#!/bin/ksh&lt;BR /&gt;set -x&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Dec 2001 18:35:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/which-scripts-are-called-by-a-particular-script/m-p/2634078#M41954</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2001-12-20T18:35:33Z</dc:date>
    </item>
  </channel>
</rss>

