Also, it would be simpler to not run the copy in a go routine until you verify that is working as expected. Then use wait groups to control the go routine lifecycle. 

On Sep 19, 2024, at 8:51 AM, Robert Engels <reng...@ix.netcom.com> wrote:


Are you certain you are running it in a terminal that has stdin available for reading?

On Sep 19, 2024, at 8:08 AM, 李世民 <buptz...@gmail.com> wrote:


The details as following link:

https://stackoverflow.com/questions/78996496/io-copyconn-os-stdin-do-not-work-as-expected#comment139289803_78996496

Please help me identify where my problem is.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/c1efd91e-2815-4a6c-b450-5d47423131c4n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/59D3B652-30F5-43B7-AA52-76D1113C9BFE%40ix.netcom.com.

Reply via email to