Hi:
>Interestingly at the beginning of acceptFactory.cc are these lines.
>
>#ifndef SO_REUSEPORT // Linux doesn't know SO_REUSEPORT
>#define SO_REUSEPORT SO_REUSEADDR
>#endif
>
>So apparently at the time procServ was written Linux did not support SO_REUSEPORT.
>
>I have 2 questions:
>
> Was there a good reason for setting this option in procServ?
Just guessing here, but I always thought REUSEADDR is useful if a server is shut down without chance to properly clean up.
The socket would then be stuck in a wait state for some time, preventing you from restarting the server.
With REUSEADDR you can start the server back up right away.
Maybe REUSEPORT was used by accident, since it actually was a #define for REUSEADDR?
-Kay
- Replies:
- RE: Problem with procServ on RHEL6 Mark Rivers
- References:
- Problem with procServ on RHEL6 Mark Rivers
- RE: Problem with procServ on RHEL6 Mark Rivers
- Re: Problem with procServ on RHEL6 Eric Norum
- RE: Problem with procServ on RHEL6 Mark Rivers
- Navigate by Date:
- Prev:
RE: Problem with procServ on RHEL6 Mark Rivers
- Next:
RE: Problem with procServ on RHEL6 Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Problem with procServ on RHEL6 Mark Rivers
- Next:
RE: Problem with procServ on RHEL6 Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|