Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Test-Run Tests Breakage on BSD Systems 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • [kag@kagnote ~]$ uname -smr
    FreeBSD 6.3-STABLE i386
    [kag@kagnote ~]$ grep PATH_MAX /usr/include/sys/syslimits.h
    #define PATH_MAX 1024 /* max bytes in pathname */
    • 1024 CYGWIN_NT-5.1 1.5.24(0.156/4/2) i686 [WinXP SP2]
      1024 FreeBSD 6.2-STABLE i386
      1024 Darwin 8.11.0 Power Macintosh [OSX 10.4.11]
      1024 Darwin 8.11.1 i386 [OSX 10.4.11]
      4096 Linux 2.4.32-grsec-opteron-peon-1.1.1 i686 [Debian ?]
      4096 Linux 2.6.9-55.ELsmp i686 [RHEL4]
      4096 Linux 2.6.18-53.1.14.el5PAE i686 [RHEL5]
      4096 Linux 2.6.22-14-generic i686 [Ubuntu 7.10]

      Interestingly, I saw the following in some cases, even on Linux: /usr/include/X11/Xwindows.h:#define PATH_MAX 1024

      I found this article very interesting:

      • Thanks!

        Interesting. I guess the original path I used was longer than 1024, but still shorter than 4096. 1024 does sound more reasonable. I guess the POSIX standard defines the minimal limit as "256" but some systems naturally have a greater value. I also know the Perl POSIX.pm contains "PATH_MAX", "_PC_PATH_MAX" and "_POSIX_PATH_MAX", but I'm not sure what the exact differences are.

        Thanks for the link. It looks interesting, but since it's kinda long, I only skimmed it so far.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.