Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Sep 2006 17:55:26 +0200
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        ru@FreeBSD.org, current@FreeBSD.org
Subject:   Re: lockf in installworld -- not a good idea
Message-ID:  <20060929155526.GA9194@garage.freebsd.pl>
In-Reply-To: <20060929141709.E70454@fledge.watson.org>
References:  <20060929141709.E70454@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 29, 2006 at 02:20:06PM +0100, Robert Watson wrote:
> I've noticed an increasing intolerance in our tools for system install an=
d maintenance to locking not being implemented over the past few years.  I =
no longer get working=20
> cron on boxes with neither rpc.lockd nor local locking enabled, for
> example. [...]

If you are refering to my change in which cron(8) started to use
pidfile(3), then I'm sorry, but you're wrong.

cron(8) from the very beginning was exiting when it had problems with
creating a pidfile, please check function acquire_daemonlock() in:

	http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/cron/lib/misc.c?rev=3D1=
=2E1&content-type=3Dtext/x-cvsweb-markup

My pidfile(3) commit is here:

	http://lists.freebsd.org/pipermail/cvs-all/2005-August/132374.html

Where I try to explain cron(8)'s behaviour.

The way I prefer is to ignore errors other than EEXIST - you can check
EXAMPLES section in the pidfile(3) manual page for more info. I just
didn't wanted to change cron(8)'s original behaviour.

I do agree, that this shouldn't be treated as critical error and I can
change it if you like.

--=20
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd@FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!

--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFFHUHuForvXbEpPzQRAptxAJwNKqMTFt6BdTBq0EHdO8ZLItZYVwCgxfQX
HSA3kSX8MQ5HOvSaF9lPWeE=
=qTCH
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060929155526.GA9194>