A couple things that might be worth trying...
# crontab -l * * * * * perl /root/nfs_share/SCRIPTS/cron_ncp.pl >>/tmp/cron_ncp.tmp +.txt 2>&1
That is, redirect output somewhere else, just to be sure there aren't permission issues, and include stderr together with stdout.
#!/usr/bin/perl use strict; use warnings; my $tmp = `ps -ef`; if ( $tmp !~ /ncp_run.tcl/ ) { my $cmd = 'expect -f /root/nfs_share/SCRIPTS/ncp_run.tcl'; print "starting now: $cmd\n"; exec $cmd; } printf "ncp_run.tcl is already running as of %s: %s\n", scalar(localti +me), $tmp );
That is, output a little more information about what's happening, and use exec instead of system (and do a bit of tidying/tightening up).

In reply to Re: perl script in nohup running from crontab by graff
in thread perl script in nohup running from crontab by tanuj

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.