From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 17:09:22 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5956D106566B for ; Fri, 10 Sep 2010 17:09:22 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 004FD8FC08 for ; Fri, 10 Sep 2010 17:09:21 +0000 (UTC) Received: by gwb15 with SMTP id 15so1127567gwb.13 for ; Fri, 10 Sep 2010 10:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nhMCGlMLUxMIIypmo66FmS2qRMKzpzTYeVUYFCLTpBg=; b=EIZaOemOLuYo/jdDdlZv95ff53E0BgovrEKdSkBBJXVef5JCYo/jPWAQYOEail01oQ 3zuyw4NB0z3FMZMUO2m8IZG/MOvRublnddoKFoHhjtAh4msJOsIfRaPDBgr6p9HkZxUY PjTKo7NgFHZjZ1TjFpPnarRFHKqFbyK6ME7cg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sHN20mCf85lm+/T8kWAc0G23fAl5m2ElNk1rCh8CtlSgD+lVdw6iN9HG7eBbFcmpb0 DMQD0MK9MpqE5cMMY2jV8ave2i0NJdENCei6i8zcot31CqMY267NyAiN4WZ95hQVmjNV mxP6S31EDAuq9qaQss3+IEqG7ZFrjpXEi57WE= MIME-Version: 1.0 Received: by 10.151.82.14 with SMTP id j14mr1161296ybl.307.1284138561106; Fri, 10 Sep 2010 10:09:21 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Fri, 10 Sep 2010 10:09:20 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Sep 2010 13:09:20 -0400 Message-ID: From: Aryeh Friedman To: Garrett Cooper Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 17:09:22 -0000 The problem with that is our version control system (devel/aegis) purposely does not allow arbitary checkins... there is a whole procedure of you have to prove it compiles and passes at least one new test and then an other person needs to review the change and then and only then can it be checked in (and even here you need to repeat the proof of build and one new test [same as the ones above] to ensure that passing the test was not a fluke of your local environment)... this project is setup so I play all 3 roles on it but all three phases have to be formally done to check it in... btw the whole goal here (unlike non-atomic VCS's like SVN [git does it to some extent] the goal here is to make sure that nothing breaks the baseline [the fully tested and reviewed repo]). On Fri, Sep 10, 2010 at 1:03 PM, Garrett Cooper wrote= : > On Thu, Sep 9, 2010 at 8:27 PM, Aryeh Friedman = wrote: >> I have a directory that must not exist on logout and rm -rf is not >> sufficent to do it because the contents need to be processed by our >> version control system. =A0 The real life scenario is our version >> control system stores the repo for a given project encrypted but for >> techinical reasons it needs to keep the checkouted files in plain text >> (they are all in the same dir) and I want to *NEVER* have the plain >> text checkouted files in my dir when I logout, *BUT* instead of just >> deleting it I need to check them in... =A0so how do I make my .logout so >> if the file exists it will not exit and give a error saying that dir >> is still there? (minor but unimportant side effect of the version >> control system is the dir will have a different name everytime it is >> made but always the same prefix) > > =A0 =A0This is probably a silly suggestion, but as I see it there is > another option: a periodic script which goes and commits the files if > the sessions go away (via crontab, or whatever). In particular, this > would solve the problem if one of the sessions you had quit, but you > had more than one session open to the machine. > =A0 =A0Of course if you didn't care about the contents of the files you > could take a different approach and employ something similar in > .login, but it doesn't sound like that's what you want to do either, > and that wouldn't solve the multi-session problem... > Cheers, > -Garrett >