Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!pyramid!csg
From: csg@pyramid.UUCP (Carl S. Gutekunst)
Newsgroups: net.bugs.uucp
Subject: Re: uucico/uuxqt bugs...howcome?
Message-ID: <614@pyramid.UUCP>
Date: Wed, 17-Sep-86 02:39:53 EDT
Article-I.D.: pyramid.614
Posted: Wed Sep 17 02:39:53 1986
Date-Received: Wed, 17-Sep-86 06:29:26 EDT
References: <900@gilbbs.UUCP> <612@pyramid.UUCP> <914@gilbbs.UUCP>
Reply-To: csg@pyramid.UUCP (Carl S. Gutekunst)
Organization: Pyramid Technology Corp., Mountain View, CA
Lines: 17

In article <914@gilbbs.UUCP> mc68020@gilbbs.UUCP (Thomas J Keller) writes:
>   Yes, well.  I have now had innumerable responses to my queries regarding
>XQT lock files.  Many people have suggested touching the file from cron.  AS
>it happens, that doesn't work.
>
>   According to a contact at a site with source license, UUCP checks the
>CREATION time, as opposed to the modification time of the lock file.

Your contact with a source license should learn to read man pages. :-)

This gets hashed out in unix-wizards every six months or so: there's no such
thing as "creation time." UUCP checks ctime, which is the the "last status
change time," literally the last time the inode changed. Since pretty darn
near anything you can do to a file changes the inode, touching the lock file
works just fine.

<csg>