How to disallow logout

Aryeh Friedman aryeh.friedman at
Fri Sep 10 17:09:22 UTC 2010

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 <gcooper at> wrote:
> On Thu, Sep 9, 2010 at 8:27 PM, Aryeh Friedman <aryeh.friedman at> 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.   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...  so 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)
>    This 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.
>    Of 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

More information about the freebsd-hackers mailing list