Re: edtf of httpd.conf corrupting file

Hello Jack,

Am 02.04.2023 um 22:15 schrieb Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

First of all, using EDTF leads to insanity and panicky postings to Midrange.

I'm using edtf regularly. No panicky post from my side ever. I'd rephrase your assertion to "know what you do". ;-)

Use vi, vim, nano, or VSCode to edit the httpd configs.

Those do not run in 5250. But in general, I agree. Edtf is merely an expedient, from today's view.

Secondly, you'd want the lines to end in 0d 0a (CR LF -- DOS) or simple 0a
(LF -- Unix) but not just simple 0d.

What is the *native* line ending of IBM i files?
- In QSYS.LIB there is none, because everything is record-oriented,
- In QDLS, it might be CRLF, because QDLS is supposed to be DOS compatible.
- In others, might be just LF to stay compatible with AIX/UNIX/Linux.

Is this correct? Do I miss something?

I have experienced that early versions of PHP and Perl sometimes fail when presented with (unexpected) CR on Linux, leading to interesting behavior as described by the OP. Of course, that was content which was uploaded by users, probably in binary mode or through scp/sftp which can't translate EOL chars as I've recently discovered. No ASCII mode.

:wq! PoC