-
Notifications
You must be signed in to change notification settings - Fork 163
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
Make startup of all elements more useful and consistent #2169
Comments
(This is an expansion of the work done in #2014) |
This should probably become a library function, at least for Go. |
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Nov 28, 2018
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Nov 30, 2018
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Nov 30, 2018
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Dec 7, 2018
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Dec 7, 2018
We have common startup messages for all go services since #2177. Most services are now go and the rest will be replaced soon, therefore this issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All elements (BS/PS/CS/DS/SIG/dispatcher/SCIONd, possibly more) should log one distinct line on startup, for example:
====================> Starting PathServer ps1-2-3
After this (or on the same line), these things should also be logged:
/proc/self/cgroups
for that)The clean exit lines should be similarly distinctive (same leader as the start line).
The text was updated successfully, but these errors were encountered: