[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#739: marked as done (MAXPATHLEN use in KDE)
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       1999-07-01 15:18:00
[Download RAW message or body]

Your message dated Thu, 01 Jul 1999 17:14:02 +0200
with message-id <377B85BA.54312866@loria.fr>
and subject line (no subject)
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at bugs) by bugs.kde.org; 18 Feb 1999 11:52:17 +0000
From dag@newtech.fi Thu Feb 18 12:52:17 1999
Received: from lupinella.troll.no ([195.0.254.19]:29233 "EHLO lupinella.troll.no" \
ident: "NO-IDENT-SERVICE") by alpha.tat.physik.uni-tuebingen.de with ESMTP id \
                <106094-7024>; Thu, 18 Feb 1999 12:51:23 +0100
Received: from laika.eunet.fi ([192.26.119.1]:39688 "EHLO laika.eunet.fi" ident: \
"NO-IDENT-SERVICE[2]") by troll.no with ESMTP id <75574-29206>; Thu, 18 Feb 1999 \
                12:50:50 +0100
Received: from dag.UUCP (uucp@localhost) by laika.eunet.fi (8.8.5/8.8.3) with UUCP id \
                NAA16330 for bugs.kde.org!bugs; Thu, 18 Feb 1999 13:45:45 +0200 (EET)
X-Mailer: exmh version 2.0.2 2/24/98
To:	bugs@bugs.kde.org
cc:	dag@newtech.fi
Subject: MAXPATHLEN use in KDE
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:	Thu, 18 Feb 1999 13:23:02 +0200
From:	Dag Nygren <dag@newtech.fi>
Message-ID: <199902181323.aa19522@dag.newtech.fi>
Return-Path: <dag@newtech.fi>
X-Orcpt: rfc822;bugs@bugs.kde.org


Package: ark
Version: 1.1

Hi again,

understood from the discussion on S_ISSOCK that you all
want to use POSIX when programming.
This would imply using pathconf() or fpathconf() to get
the maximum PATH length possible... ;-)
However I see MAXPATHLEN used the "good old way" in
many places.
Once again SCO gives a problem by not defining MAXPATHLEN
at all. 

Extract from  /usr/include/limits.h:

/*
 * The following are not defined since the value can vary according
 * to the file referred to.
 *
 * In all cases, pathconf should be checked to find the actual value for
 * a particular file.
 *
 *      LINK_MAX                _PC_LINK_MAX    _POSIX_LINK_MAX
 *      NAME_MAX                _PC_NAME_MAX    PATHSIZE
 *      PATH_MAX                _PC_PATH_MAX    PATHSIZE
 *      PIPE_BUF                _PC_PIPE_BUF    _POSIX_PIPE_BUF
 *
 *  A similar rationale applies to the following cross compatibility values.
 *
 *      MAXPATHLEN              (from 4.2 BSD params.h)
 */

It is easy enough (and probably quite safe) to insert a
#ifndef MAXPATHLEN
#define MAXPATHLEN 1024
#endif

But if you really are into POSIX ....

BTW. Are you really sure that S_ISSOCK() is POSIX?
SCO:s manpage on stat() claims that it is ocnformant toPOSIX:
  IEEE POSIX Std 1003.1-1990 System Application Program Interface (API) [C
  Language] (ISO/IEC 9945-1) ;
  and NIST FIPS 151-1 .


BRGDS

Dag Nygren
-- 
Dag Nygren                               email: dag@newtech.fi
Oy NewTech Ab                            phone: +358 9 8024910
Trasktorpet 3                              fax: +358 9 8024916
02360 ESBO                                 NMT: 0400-426312
FINLAND


[prev in list] [next in list] [prev in thread] [next in thread]