-
-
Notifications
You must be signed in to change notification settings - Fork 584
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
fix --write-pid-path is no effective #492
Conversation
Codecov Report
@@ Coverage Diff @@
## next #492 +/- ##
==========================================
- Coverage 36.85% 36.84% -0.02%
==========================================
Files 45 45
Lines 8907 8918 +11
==========================================
+ Hits 3283 3286 +3
- Misses 5624 5632 +8
|
@jialeens Thanks for the PR!. You also need to handle this option coming from command line. |
@yshui |
src/options.c
Outdated
@@ -700,6 +700,11 @@ bool get_cfg(options_t *opt, int argc, char *const *argv, bool shadow_enable, | |||
case 322: | |||
// --logpath, --log-file | |||
free(opt->logpath); | |||
if (*optarg != '/') { | |||
log_error("The --log-file in your configuration file is not" |
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.
there is no requirement for --log-file
to be an absolute path.
Sorry, closed by mistake |
Pushed your changes to |
OK, I see it. |
fix --write-pid-path is no effective
the --write-pid-path is no effective,When picom is started, the configuration --write-pid-path is not read.
When picom exiting, remove the pid file.