Mount.s3ql with --log argument still creates default log file

[GoogleCodeExporter]

Hi,

When using mount.s3ql with the --log argument, to specify an alternative 
location for the mount log file, it appears a log file is still first created 
at the default location ~/.s3ql/mount.log. The default file is then correctly 
not used and stays at 0 byte size, but it is nevertheless created in an 
undesired location.

This doesn't seem like intended behavior, but I haven't seen it being reported 
previously.

Original issue reported on code.google.com by nicola.c...@gmail.com on 23 Sep 2013 at 10:33

[GoogleCodeExporter]

Original comment by Nikolaus@rath.org on 24 Sep 2013 at 4:22

• Changed state: Accepted
• Added labels: Type-Bug

[GoogleCodeExporter]

This issue was closed by revision 722ade93ec11.

Original comment by Nikolaus@rath.org on 3 Oct 2013 at 5:10

• Changed state: Fixed