-
Notifications
You must be signed in to change notification settings - Fork 41
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
ttybus losing some bytes #17
Comments
Found this: ➜ ls -ltr /dev/ttyGNSS*
srwxrwxrwx 1 root root 0 Nov 12 11:17 /dev/ttyGNSS_mux
lrwxrwxrwx 1 root root 10 Nov 12 11:17 /dev/ttyGNSS_fake_a.bak -> /dev/pts/0
lrwxrwxrwx 1 root root 10 Nov 12 11:17 /dev/ttyGNSS_fake_b -> /dev/pts/1
lrwxrwxrwx 1 root root 10 Nov 12 19:15 /dev/ttyGNSS_fake_a -> /dev/pts/1 <== this should not be /1 As I could understand, my main service that creates the For some reason, the service that creates I am not sure if this is caused by the way I use ttybus, but I am sharing this here to follow the discussions. I am using it this way: # Service 1
tty_bus -d -s /dev/ttyGNSS_mux
tty_attach -s /dev/ttyGNSS_mux /dev/ttyUSB0
# Sevice 2
tty_fake -o -s /dev/ttyGNSS_mux /dev/ttyGNSS_fake_a &
# Sevice 3
tty_fake -o -s /dev/ttyGNSS_mux /dev/ttyGNSS_fake_b & |
I was using the flag |
Removing this Is there any way to monitor the created socket? I could not find any tool for that, just the |
I think I understood what was going on with my application.
The tty_mux socket might be filling its buffer after some time, and then things do not work well anymore.
Found out that the
BUFFER_SIZE
is 4096.ttybus currently doesn't have a way to change this value from the command line, but I am not sure yet if increasing it will make any difference since my app will be running for a long time and the issue will eventually happen again
Do you have a suggestion for what I could do in this case?
I started my issue here, #14 (comment). Well, I am opening a new issue instead of hijacking the other one.
The text was updated successfully, but these errors were encountered: