i've been rewriting a script that i use to parse the (text) results file from a lab instrument and insert the results in a postgresql database. the machine on which the log is stored is an nt 4 workstation, i mount a read-only share to read the file on the linux box i use to run the script (smbfs 2.2.1 on a debian box)

my decision to rewrite the script was motivated by some difficulty in getting certain sets of lines to parse appropriately ... now that i've been starting to debug the structure of the new version i've noticed that if i step through the script using ptkdb to reach a certain point the file is read appropriately, but if i set that same point in the script as a break point and run straight to it i'm a line further down in the source file. this led me to start wondering how smbfs handles new lines. i've done some looking around and discovered that samba in its default configuration makes no changes in the line endings when creating a share, but i haven't been able to find anything about how smbfs handles newlines when mounting nt shares. i had a klunky little procedure that i had created in the previous version to iron out anomalous behavior, but i'm not sure that i caught all of that and i'd like to make this version a little cleaner. has anyone else dealt with this?

In reply to a little OT - smbfs weirdness by ralphie

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.