Hi all,

we are writing from Baan to an NFS-Drive. We don't use special characters, just use "seq.puts()" with our string in found our files equipped with CRLF.
Yesterday we had a crash, among others, also with that NFS-drive.
Today we noticed, that our files "end of lines" only are only LFs.

I tried unchanged Programms, which worked fine tall the time, but the output of them also contains only a LF not a CRLF as desired.

Is it possible, that this has something to do with the NFS-drive?

Thanks:confused:

In windows lines are written with CRLF and in unix its only with LF . U can use dos2unix or transfer the files in ascii mode to do conversion among these 2 different way of writing lines .

Hi,

Are you directly writing on the NFS-Drive? Or are you writing it on the server then copying it?
Are you adding chr$(13) manually to the end of every line?

- George

Hi all,

for the first: Thanks for your support!

The thing is: People told me that there was a CRLF before the NFS-Drive crashed. Meanwhile I'm not so sure, that this is right, because I checked an other (productive) system, where I also only found LFs.

The technique: The program writes directly to the NFS-drive, there is no copy at all. There is also no chr$(13) in the program.

Because people told me there was a CRLF <BEFORE THE CRASH> I thought maybe it's done somehow by the NFS-Drive.
Meanwhile I think my information was wrong, because in the program is no chr$(13) and NFS doesn't handle "end of lines"!

So my conclusion is NFS couldn't cause the problem!

Hi there,

man mount:
<...snip...>

Mount options for fat
(Note: fat is not a separate filesystem, but a common part
of the msdos, umsdos and vfat filesystems.)


conv=b[inary] / conv=t[ext] / conv=a[uto]
The fat file system can perform CRLF<-->NL (MS-DOS
text format to UNIX text format) conversion in the
kernel. The following conversion modes are avail­
able:

binary no translation is performed. This is the
default.

text CRLF<-->NL translation is performed on all
files.

auto CRLF<-->NL translation is performed on all
files that don't have a "well-known binary"
extension. The list of known extensions can
be found at the beginning of fs/fat/misc.c
(as of 2.0, the list is: exe, com, bin, app,
sys, drv, ovl, ovr, obj, lib, dll, pif, arc,
zip, lha, lzh, zoo, tar, z, arj, tz, taz,
tzp, tpz, gz, tgz, deb, gif, bmp, tif, gl,
jpg, pcx, tfm, vf, gf, pk, pxl, dvi).

hth

Norbert