Skip to content

Conversation

agebhar1
Copy link
Contributor

If the content of PID_FOLDER is not valid it falls back to /tmp without any
notification. This holds for LOG_FOLDER too. Added a warning message to notify
the user in such a case.

In order to use colored console messages on initializing PID/LOG locations
moved the functions above.
If the content of `PID_FOLDER` is not valid it falls back to `/tmp` without any
notification. This holds for `LOG_FOLDER` too. Added a warning message to notify
the user in such a case.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 19, 2018
@wilkinsona wilkinsona added the status: waiting-for-feedback We need additional information before we can continue label Sep 19, 2018
@wilkinsona
Copy link
Member

Thanks for the PR. I'm not sure a warning is warranted in either case, at least not in the default launch script. Can you please explain why you think the warnings are warranted?

@agebhar1
Copy link
Contributor Author

Sure.

In a customer setup each service has the same directory layout with a directory for logging and pid file. The service name is also identical across all services. Only the base directory is the name of the service itself.

Unfortunately for two new services the directories for the pid folder didn't exists such that the PID file was located at /tmp. Each time one service was started it overrides the file of the other one. I took some time to figure it out. A warning message about the fallback/reconfiguration (it's not the standard case) to /tmp had saved time.

The warning message only appears if the value of PID_FOLDER (LOG_FOLDER) exists but is not valid (executable).

@philwebb philwebb added the for: team-attention An issue we'd like other members of the team to review label Sep 23, 2018
@agebhar1
Copy link
Contributor Author

@wilkinsona is the feedback ok for you?

@philwebb philwebb changed the title add a warning message if PID/LOG location uses fallback Add a warning message if PID/LOG location uses fallback Sep 26, 2018
@philwebb philwebb added type: enhancement A general enhancement for: merge-with-amendments Needs some changes when we merge and removed for: team-attention An issue we'd like other members of the team to review status: waiting-for-feedback We need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Oct 3, 2018
@philwebb philwebb added this to the 2.1.x milestone Oct 3, 2018
@wilkinsona
Copy link
Member

Yes, thank you. We plan to include the proposed changes in 2.1.

@wilkinsona wilkinsona self-assigned this Oct 4, 2018
@wilkinsona wilkinsona closed this in 4a222cb Oct 4, 2018
wilkinsona added a commit that referenced this pull request Oct 4, 2018
* gh-14519:
  Polish "Log a warning when using fallback for pid and log locations"
  Log a warning when using fallback for pid and log locations
@wilkinsona
Copy link
Member

Thank you for making your first contribution to Spring Boot, @agebhar1. The proposed changes have been merged into master.

@wilkinsona wilkinsona modified the milestones: 2.1.x, 2.1.0.RC1 Oct 4, 2018
@agebhar1 agebhar1 deleted the feature/launch.script branch October 4, 2018 17:29
@agebhar1
Copy link
Contributor Author

agebhar1 commented Oct 4, 2018

Thank you @wilkinsona 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: merge-with-amendments Needs some changes when we merge type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants