Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Output to /dev/tty #69
Well, that's something I coded in the early development stage of raspiBackup. As far as I remember it was somehow related to the fact that the output is written in parallel into the log.
What's your exact use case? I guess you want to pipe the output somewhere in your code when invoking raspiBackup. @christianTF Please confirm.
I will check whether I can change the code to use stdout and stderr for all messages.
As the LoxBerry uses native logging facilities with live web logviewer, I tried to pipe the output directly to the LogBerry logging instead of copying it after the backup.
Finally I found the tool
This is a working solution where I don’t require any adaption/feature. It too would be compatible with stdout in the case you are thinking of a modification.
I was just asking because I’ not familiar with tty output.
Glad you found a solution for your issue. I suggest to create an issue first next time you face some strange behavior of raspiBackup before spending time to find a workaround
Usage of tty does not comply to standard io handling of programs. I frankly didn't care about this in early development stages. But you put a valid issue on the table. I found out it's not that difficult to redirect I&W messages into stdout and E messages into stderr.
works already in a prototype. Is this what you are looking for and will help you to get rid of your workaround?
I keep you posted in this issue when there is a fix available. I will roll in this fix in next release and then it's up to you whether you want to stick with your workaround or use stdout and stderr.
Glad to hear that's what you need
This feature is already available in the development branch which will become the next release. Feel free to grab the code and test right now. Please note: The development branch includes all issues marked as