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

yarprun service on TEO network PCs does not always connect to teo-main yarp server #43

Closed
jgvictores opened this issue Jun 28, 2016 · 2 comments
Closed

yarprun service on TEO network PCs does not always connect to teo-main yarp server #43

jgvictores opened this issue Jun 28, 2016 · 2 comments
Assignees
@jgvictores
Labels
bug Something isn't working duplicate

Comments

@jgvictores
Copy link
Member

The current use of daemontools makes yarprun run sometimes without connecting to the yarp server, which causes problems such as #42.
A yarp detect or similar (checking the return value) should be included in the daemontools service script (/etc/service/yarprun) or even completely replace daemontools for a different method to avoid this.
@jgvictores jgvictores changed the title Improve yarprun initialization on TEO network PCs yarprun service on TEO network PCs does not always connect to teo-main yarp server Jun 28, 2016
@jgvictores jgvictores added the bug Something isn't working label Jun 28, 2016
@jgvictores jgvictores mentioned this issue Jun 28, 2016
Closed
@jgvictores jgvictores self-assigned this Jul 23, 2016
@jgvictores
Copy link
Member Author

Should move this issue somewhere.

@jgvictores jgvictores mentioned this issue May 5, 2017
Open
@jgvictores
Copy link
Member Author

This issue was moved to roboticslab-uc3m/teo-main#10

@PeterBowman PeterBowman closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgvictores jgvictores

Labels
bug Something isn't working duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jgvictores @PeterBowman