Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 5 Mar 2002 14:17:45 -0500 (EST)
From: Michael Adler <adler AT glimpser DOT org>
To: Corinna Vinschen <cygwin AT cygwin DOT com>
Subject: Re: cron problem
In-Reply-To: <20020305100106.L13590@cygbert.vinschen.de>
Message-ID: <Pine.NEB.4.44.0203051415390.29991-100000@reva.sixgirls.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Tue, 5 Mar 2002, Corinna Vinschen wrote:

> On Thu, Feb 28, 2002 at 10:49:51AM -0500, Michael Adler wrote:
> > What I think should really happen is that cron should create those
> > directories during installation so they are owned by whoever installed
> > cygwin.
>
> Would you mind to help out and create an install script for
> /etc/postinstall?


I thought you could just inlude empty directories when you make the tar
ball.

This worked for me too.
############################

#!/bin/bash

if [ -d /var/cron/tabs ] ; then
        echo "/var/cron/tabs already exists"
else
        echo "creating /var/cron/tabs"
        mkdir -p /var/cron/tabs
fi




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/