I'm on perl, version 5.005_03 built for i386-freebsd...the code is as follows: 
open(FH,"+<./file.dat") || die("Can't open ./file.dat for reading/writ
+ing: $!");
flock(FH,LOCK_EX);
seek(FH,0,0);
@dat = <FH>;
foreach (@dat) {chomp}
# this is where I process @dat, and when I feed text 
# manually into it, it works.  the problem doesn't
# lie in this segment of the code
seek(FH,0,0);
print FH join("\n",@dat);
flock(FH,LOCK_UN);
close(FH);

[download]
Now, i can open the file for reading, and i can open it for writing, and both work fine. But when I try reading AND writing, it doesnt spring an error, it simply doesnt read anything from or write anything to the file. Should I try +>instead of +<or what?

In reply to Re: Re: FreeBSD reading/writing workaround? by Anonymous Monk
in thread FreeBSD reading/writing workaround? by Anonymous Monk

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.