There's not enough information for me to test your code; however, this condition strikes me as potentially problematic:

index($buf, "/DATA_String/") > 0
[download]

In "index STR,SUBSTR,POSITION", the POSITION is zero-based. Perhaps you want:

index($buf, "/DATA_String/") > -1
[download]

Consider this code:

$ perl -E '
    my @strings = qw{
        no_data_string
        /DATA_String/
        X/DATA_String/
        /some/path/to/DATA_String/
    };

    say "-" x 40;

    for my $string (@strings) {
        say "\$string[$string]";

        for my $pos (qw{0 -1}) {
            say "\$pos[$pos]";

            if (index($string, "/DATA_String/") > $pos) {
                say "index() TRUE";
            }
            else {
                say "index() FALSE";
            }
        }

        say "-" x 40;
    }
'
[download]

Output:

----------------------------------------
$string[no_data_string]
$pos[0]
index() FALSE
$pos[-1]
index() FALSE
----------------------------------------
$string[/DATA_String/]
$pos[0]
index() FALSE
$pos[-1]
index() TRUE
----------------------------------------
$string[X/DATA_String/]
$pos[0]
index() TRUE
$pos[-1]
index() TRUE
----------------------------------------
$string[/some/path/to/DATA_String/]
$pos[0]
index() TRUE
$pos[-1]
index() TRUE
----------------------------------------
[download]

"I am new to socket programming but found an example in O’Reilly’s “Advanced Perl Programming”. After adjusting the code for my network, ..."

"Advanced Perl Programming" is an excellent book, I own a copy myself; however, it was published over a quarter of a century ago. Here's some suggestions for aligning your code with modern practices:

• Check for I/O exceptions — I'd recommend the autodie pragma.
• Use a lexical variable for the filehandle in the smallest scope possible (see open()).
• Avoid "Indirect Object Syntax".

So, your code might become something like this:

...
use strict;
use warnings;
use autodie;

use IO::Socket;

{
    open my $pid_fh, '>', '/var/run/aws.rcvr.pid';
    print $pid_fh "$$\n";
}

my ($sock, $new_sock, $buf );
$sock = IO::Socket::INET::->new(...);
...
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.