-
March 29th, 2017, 03:29 AM
#16
Re: WinSock listen() method seems to be blocked only after a reboot
Depends upon what credentials are used from Task Scheduler to start the program. Why are you starting it from Task Manager rather than the more usual ways of starting a program when someone logs on.
All advice is offered in good faith only. All my code is tested (unless stated explicitly otherwise) with the latest version of Microsoft Visual Studio (using the supported features of the latest standard) and is offered as examples only - not as production quality. I cannot offer advice regarding any other c/c++ compiler/IDE or incompatibilities with VS. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/ and can be used without reference or acknowledgement. Also note that I only provide advice and guidance via the forums - and not via private messages!
C++23 Compiler: Microsoft VS2022 (17.6.5)
-
March 29th, 2017, 05:08 PM
#17
Re: WinSock listen() method seems to be blocked only after a reboot
-
March 29th, 2017, 08:16 PM
#18
Re: WinSock listen() method seems to be blocked only after a reboot
OK. A follow up. Please disregard what I said above... I got it solved.
It was a race condition in my app. It was reading the port number into a local cache variable after the thread that uses that variable was started, thus creating a race condition.
Thanks everyone who pitched in!
PS. I was able to verify it by using this tool.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|