To avoid supplying ssh password, use a ssh key with a key-agent. Also, do a search around these parts related to logging on to a ssh host & running commands.

Use some kind of configuration -- hash, external files, __DATA__, etc -- to associate processes to a server ...

# Untested, incomplete code.

my %map =
  ( 'host-p' => [qw[ cron apache ]]
  , 'host-q' => [qw[ ntpd ]]
  );

for my $host ( sort keys %map )
{
  #  Log on $host at this point.

  #  Check processes.
  foreach my $proc ( @{ $map{ $host } } )
  {
    printf qq[%s: %3s running]
      , $proc
      , check_proc( $proc ) ? '' : 'not' ;
  }

  #  Log off.
}

sub check_proc
{
  my ( $proc ) = @_;

  my $ps = make_ps( $proc );
  my $res = qx[ $ps ];
  # Check $? for cause of failure if you care.

  return
    defined $res && $res =~ m{ \b psname = $proc \b }x;
}

sub make_ps
{
  return sprintf q[ps -ef | grep psname=%s] , $_[0] ;
}
[download]

Your process checking looks too complicated; there might be OS specific commands/options that won't require filtering of ps run itself. Perhaps some native Perl module may be in existence for the purpose.

Your process checking looks too complicated; there might be OS specific commands/options that won't require filtering of ps run itself. Perhaps some native Perl module may be in existence for the purpose.

Day 17: Checking process existence and listing processes (Proc::Find) mentions pgrep & Proc::Find to find a process by name, among other ways.