I've used a symlinking approach allowing the real script to see how it was called, using a dispatch table.. perhaps this will work for your purposes:

Create a script for example /usr/sbin/myscript.pl 
#!/usr/bin/perl

use strict;
use warnings;

my $ME = $0 ;
$ME =~ s@^\.\/|\/.*\/@@g;
$ME =~ /myscript.pl/ and die ("\n Please dont call me directly!\n\n");

my %workerscripts = ( 'worker01'  => \&worker01,
                      'worker02'  => \&worker02,
                      'worker03'  => \&worker03
                    );

my $real_command  = $workerscripts{&findME};
&$real_command;



#---
sub findME
{
   while ( my($k,$v) =  each %workerscripts )
   {
      return $k if $k =~ /$ME/ ;
   };
};

sub worker01
{ print "worker01 was called\n"; exit 0; };

sub worker02
{ print "worker02 was called\n"; exit 0; };

sub worker03
{ print "worker03 was called\n"; exit 0; };

[download]


Then create links to that script: 
cd /usr/bin/
ln -s /usr/sbin/myscript.pl worker01
ln -s /usr/sbin/myscript.pl worker02
ln -s /usr/sbin/myscript.pl worker03

[download]
Invoke /usr/bin/worker01, worker02, or worker03 and the proper subroutine should be called..

Does that get you closer?
-Harold

In reply to Re^3: custom name to the process by hsinclai
in thread custom name to the process by rimvydazas

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.