tries to write log files to the location of the executable

[iamsmooth]

simplewallet (and maybe bitmonerod?) uses the location of the executable to store the log files. This might be normal for Windows, but is clearly broken for linux (where executable would normally go in some non-writeable bin) and probably mac too.

In the case of simplewallet it is reasonable for the log file to go the same place as the wallet file. bitmonerod might write its log file into .bitmonero although a package manager build should probably go to a standard log location, so there should be a build option for this.

[sammy007]

I'd like to suggest naming pattern: /wallet/file/location/{wallet_file_name}.log

[tewinget]

For nix my goto is /var/log/

As for Windows, not sure what the default is...

At any rate, very valid point(s). Thanks.
On Dec 5, 2014 12:29 AM, "Sammy Libre" notifications@github.com wrote:

I'd like to suggest naming pattern:
/wallet/file/location/{wallet_file_name}.log

—
Reply to this email directly or view it on GitHub
#194 (comment)
.

[iamsmooth]

/var/log certainly makes sense for bitmonerod, although for simplewallet there is something to be said for sammy's suggestion, since it is a user app and not a system app, plus that is the only way to get a history of transactions performed. No matter what though, putting it with the bin is definitely wrong for linux

[netmonk]

would be interesting to add a --log-file options when running multiples instances on the same machine

[iamsmooth]

Yes there should definitely be a log-file option. My earlier comments were about where the default should go.

[netmonk]

/var/log sounds good :)

[netmonk]

but should use syslog facility, to deal with write permission in /var/log.
So option should be provided to target which facility to use in syslog.

Or the make install under root, should deal with file creation in /var/log and setting correct permission for running bitmonerod without root priviledges

[fluffypony]

I believe this is fixed now with the latest batch of merges.