You might want to show that example (just to make it more generally usable "as
is"), with the variable bound in single-quotes, e.g.:
<Extension fileop>
Module xm_fileop
# Check the size of our log file every hour and rotate if it is
larger than 1Mb
<Schedule>
Every 1 hour
Exec if (file_size('%LOGFILE%') >= 1M)
file_cycle('%LOGFILE%', 5);
</Schedule>
# Rotate our log file every week on Sunday at midnight
<Schedule>
When @weekly
Exec file_cycle('%LOGFILE%', 5);
</Schedule>
</Extension>
If you attempt to put this in place, to prevent "expand forever" logging on a
Windows system (using the current document example), then you immediately get
bitten by the spaces in the typical Program Files folder, and (of course) if
you then think of quoting it, and make the mistake of starting with
double-quotes, then all of those backslashes get "eaten", or in some cases, get
interpreted as newline characters. The above syntax should work in either OS
environment, but saves someone the headache of the Windows-related issues.
FWIW.
Marvin Nipper
The information transmitted, including any content in this communication is
confidential, is intended only for the use of the intended recipient and is the
property of The Western Union Company or its affiliates and subsidiaries. If
you are not the intended recipient, you are hereby notified that any use of the
information contained in or transmitted with the communication or
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify the
Western Union sender immediately by replying to this message and delete the
original message
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
nxlog-ce-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users