From owner-freebsd-arch@FreeBSD.ORG Thu Aug 25 14:47:41 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C06316A41F; Thu, 25 Aug 2005 14:47:41 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id E744343D45; Thu, 25 Aug 2005 14:47:39 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id j7PElaCE061623; Thu, 25 Aug 2005 18:47:36 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id j7PElZgt061622; Thu, 25 Aug 2005 18:47:35 +0400 (MSD) (envelope-from yar) Date: Thu, 25 Aug 2005 18:47:35 +0400 From: Yar Tikhiy To: Pawel Jakub Dawidek Message-ID: <20050825144735.GA59955@comp.chem.msu.su> References: <20050822213028.GB4812@garage.freebsd.pl> <20050823080754.GA47261@garage.freebsd.pl> <20050823202656.GB30465@funkthat.com> <20050824134540.GA94265@comp.chem.msu.su> <20050824171437.GA755@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050824171437.GA755@garage.freebsd.pl> User-Agent: Mutt/1.5.9i Cc: FreeBSD-arch Subject: Re: New library: libpidfile. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Aug 2005 14:47:41 -0000 On Wed, Aug 24, 2005 at 07:14:37PM +0200, Pawel Jakub Dawidek wrote: > On Wed, Aug 24, 2005 at 05:45:40PM +0400, Yar Tikhiy wrote: > +> > > +> > Neither, of these are safe to prevent multiple daemons from starting > +> > up at the same time... Both NetBSD and OpenBSD doesn't even check if > +> > a daemon is running.. it just blindly splats the pid into the file.. > +> > +> Of course, giving advices is much easier than doing the real work, > +> but I dare suggest cooperation with NetBSD and OpenBSD on this issue > +> so that eventually we have a good and compatible implementation of > +> the pidfile API in *BSD. I believe that the NetBSD and OpenBSD > +> folks won't take offence if approached with a well-grounded explanation > +> of why their current pidfile functions suck. > > They are of course free to adpot pidfile(3) and I'll gladly provide > all needed explanations if they'll ask me. And what if they miss your effort and don't ask you in the first place? My point is that a bit of good will won't hurt when we see evidently rotten code in other projects and have a better solution to offer. This is particularly true for *BSD since we all grow from the same root. In addition, by taking the initiative you'll encourage *BSD folks to provide useful feedback on your work. To my mind, it is a wonderful opportunity that as little as a mere email can help to make *BSD a tad better and more compatible. -- Yar