From owner-freebsd-hackers Mon Jul 23 18:21: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kzsu.stanford.edu (KZSU.Stanford.EDU [171.66.118.90]) by hub.freebsd.org (Postfix) with ESMTP id 7BF6437B405 for ; Mon, 23 Jul 2001 18:21:00 -0700 (PDT) (envelope-from romain@kzsu.stanford.edu) Received: (from romain@localhost) by kzsu.stanford.edu (8.11.4/8.11.4) id f6O1L0p17808 for hackers@FreeBSD.ORG; Mon, 23 Jul 2001 18:21:00 -0700 (PDT) (envelope-from romain) Date: Mon, 23 Jul 2001 18:21:00 -0700 (PDT) From: Romain Kang Message-Id: <200107240121.f6O1L0p17808@kzsu.stanford.edu> To: hackers@FreeBSD.ORG Subject: pkg_add puzzlement Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been using this in a PLIST: 1 @exec test -d %D/var/run/procstates || mkdir -p %D/var/run/procstates 2 @exec chown root.wheel %D/var/run/procstates && chmod 1775 %D/var/run/procstates The rationale for each line: - 1 Install: make sure that the directory exists, avoiding error messages if an earlier instance of the package is on the machine. - 2 Install: make sure directory has correct permissions. For some reason, there are machines where the package is added, but /var/run/procstates does not get created. pkg_add has no complaints. I've looked at the package, root's login environment, and the pkg_add source code, but I don't see any reason for this anomaly. Suggestions, anyone? Thanks, Romain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message