Skip to content
Snippets Groups Projects
  1. Mar 15, 2019
  2. Mar 14, 2019
  3. Feb 11, 2019
  4. Dec 22, 2018
  5. Aug 19, 2018
  6. Jul 17, 2018
  7. May 11, 2018
  8. Mar 10, 2018
  9. Mar 09, 2018
  10. Mar 08, 2018
  11. Feb 14, 2018
  12. Jan 24, 2018
  13. Jan 17, 2018
  14. Dec 28, 2017
  15. Dec 27, 2017
  16. Dec 07, 2017
  17. Feb 26, 2017
  18. Feb 23, 2017
  19. Feb 16, 2017
  20. Jan 11, 2017
  21. Aug 31, 2016
    • Birte Kristina Friesel's avatar
    • Niclas Zeising's avatar
      Only use sysconf() if HOST_NAME_MAX is undefined · 5ab630b5
      Niclas Zeising authored
      On some systsems sysconf() can return a very large value, unsuitable for
      use with malloc().  Only use sysconf() if HOST_NAME_MAX isn't avalable.
      5ab630b5
    • Niclas Zeising's avatar
      Fix build on FreeBSD. · 873c84f0
      Niclas Zeising authored
      FreeBSD lacks the constant HOST_NAME_MAX, instead using sysconf(3) to
      find out the value of the maximum host name length at run time.  Patch
      to use this instead of HOST_NAME_MAX.
      This brings with it the need to use malloc instead of using a statically
      sized buffer for the host name, since the size of the buffer cannot be
      known at run time.  Errors from sysconf or malloc just means that the
      entire block of code is skipped over (the same way it's skipped if the
      call to gethostname() fails), rather than returning any kind of error to
      the caller or logging an error message somewhere.
      873c84f0
  22. Aug 28, 2016
  23. Aug 27, 2016
  24. Apr 24, 2016
  25. Apr 16, 2016
  26. Apr 14, 2016
  27. Apr 13, 2016
Loading