1. 02 Aug, 2017 1 commit
    • Linus Nordberg's avatar
      Use a listen(2) backlog of 128. · 950306fc
      Linus Nordberg authored
      There's a chance that incoming (legitimate) connections arrive faster
      than what it takes to spawn a new thread and get back to
      listen(). Therefore we should ask the stack to queue at least one
      entry, i.e. use a backlog value of at least 1. There's arguable also a
      chance of more than two concurrent incoming connections, which would
      make a case for a backlog value greater than one.
      
      A reasonable high value seems to be 128, which also is what SOMAXCONN
      is on many unix systems. In the choice between 1 and 128, an argument
      against the higher value is that it may mask the potential problem of
      spending a long time serving incoming connections.
      
      Being reasonably confident that radsecproxy is efficient when it comes
      to serving incoming connections, by handing them off to a newly
      spawned thread, I think that 128 is a fine choice.
      
      Closes RADSECPROXY-72.
      950306fc
  2. 21 Sep, 2016 1 commit
  3. 19 Sep, 2016 1 commit
  4. 16 Jan, 2015 1 commit
  5. 02 Sep, 2013 1 commit
  6. 17 Apr, 2012 1 commit
  7. 26 Sep, 2011 1 commit
  8. 23 Mar, 2010 1 commit
  9. 08 Mar, 2010 1 commit
  10. 27 Jan, 2009 1 commit
  11. 07 Jan, 2009 1 commit
  12. 22 Dec, 2008 1 commit
  13. 19 Dec, 2008 3 commits
  14. 18 Dec, 2008 1 commit
  15. 24 Sep, 2008 2 commits
  16. 23 Sep, 2008 1 commit
  17. 17 Sep, 2008 2 commits
  18. 16 Sep, 2008 2 commits
  19. 11 Sep, 2008 1 commit
  20. 21 Aug, 2008 2 commits