-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrict log file creation to 'vast start' #803
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not yet seem to handle vast -N
, does it? Haven't tested yet, just had a glance at the code.
Yes, by design: The overall goal was that commands issued by the user in his terminal should not pollute the current working directory by creating a vast log directory, which would include |
Yes, since it is basically running |
4b26fe5
to
35ad34a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be working nicely. Just a few small things I've noticed.
I added a commit addressing ch13324 into this PR as well, since both stories are closely related to the logging behaviour of caf and touch the same code anyways. |
Set file verbosity to 'quiet' by default, and do not create a log file and log directory when file verbosity is set to 'quiet'. Set file verbosity to 'debug' by default only for the 'vast start' subcommand.
The config options 'vast.log-directory' was deprecated and replaced by 'vast.log-file'. If specified, all log files will be written to the specified file.
Set file verbosity to 'quiet' by default, and do not create a log file and log directory when file verbosity is set to 'quiet'.
Set file verbosity to 'debug' by default only for the 'vast start' subcommand.