Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use well known non-existent name for socket specs #4206

Merged
merged 1 commit into from Mar 30, 2017
Merged

Use well known non-existent name for socket specs #4206

merged 1 commit into from Mar 30, 2017

Conversation

jhass
Copy link
Member

@jhass jhass commented Mar 28, 2017

Should fix #4130

Not giving a FQDN makes us rely on environment configuration too much, for example there might a search domain configured where the host becomes valid in some way.

@asterite
Copy link
Member

@jhass Thank you! And welcome back! 😄

@asterite asterite merged commit 0b3f7e5 into master Mar 30, 2017
@jhass jhass deleted the feature/socket_spec_hostnames branch March 30, 2017 15:20
@bcardiff bcardiff added this to the 0.22.0 milestone May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.22.0
Development

Successfully merging this pull request may close these issues.

socket_spec.cr:541 fails in Arch Linux chroot environment
3 participants
@jhass @asterite @bcardiff