--===============1047097254==
Content-Type: multipart/alternative;
boundary="=====================_240704156==.ALT"

--=====================_240704156==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 10:07 AM 11/1/2007, Paul wrote:
>How can I get the transfer log to record spaces for spaces instead of it
>subsituting spaces for underscores? I see that the system log does this
>by default, but I really need the transfer log to do this because I have
>some scripts working with the file and need to differentiate between a
>real underscore and a space. And if I do this, is there another unique
>character I can have proftpd handle this, so at least I know what a space
>is a space and an underscore is an underscore???


Ah, so the code from my 2006-11-30 email to you didn't work for
you? That is, trying to use underscores as wildcards to find matches
for the 'real' filename was not going to work?

The use of underscores in filenames in that log is because log
parsers use spaces to break the log entries into individual
fields. If spaces in filenames are passed into the log it will break
log parsers.

That said, if nothing else will use the log you can do as you wish.

There doesn't appear to be a configuration statement to affect
this. The code looks to be in src/xferlog.c routine xferlog_write
.. I haven't tried this, but it looks like you could change the line
containing the '_' to use some other character. Indeed, you could
possibly take out that for-loop.

--=====================_240704156==.ALT
Content-Type: text/html; charset="us-ascii"



At 10:07 AM 11/1/2007, Paul wrote:

How can I get the transfer log
to record spaces for spaces instead of it

subsituting spaces for underscores?  I see that the system log does
this

by default, but I really need the transfer log to do this because I
have

some scripts working with the file and need to differentiate between
a

real underscore and a space.  And if I do this, is there another
unique

character I can have proftpd handle this, so at least I know what a
space

is a space and an underscore is an underscore???


Ah, so the code from my 2006-11-30 email to you didn't work for
you?  That is, trying to use underscores as wildcards to find
matches for the 'real' filename was not going to work?


The use of underscores in filenames in that log is because log parsers
use spaces to break the log entries into individual fields.  If
spaces in filenames are passed into the log it will break log
parsers.


That said, if nothing else will use the log you can do as you wish. 



There doesn't appear to be a configuration statement to affect
this.  The code looks to be in src/xferlog.c routine xferlog_write
..  I haven't tried this, but it looks like you could change the line
containing the  '_' to use some other character.  Indeed, you
could possibly take out that for-loop.




--=====================_240704156==.ALT--



--===============1047097254==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
--===============1047097254==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ProFTPD Users List
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html
--===============1047097254==--