config file under RCS

Sebastien Estienne sebastien.estienne at
Tue Dec 20 10:13:57 UTC 2005

2005/12/20, Fabio Massimo Di Nitto <fabbione at>:
> Please keep mails on the mailing list so that everybody can partecipate.
> There is no sensible of private information in this thread.

It was just a mistake, when i hitted the reply button, i never want to
make the thread private, sorry.

> Sebastien Estienne wrote:
> > 2005/12/20, Fabio Massimo Di Nitto <fabbione at>:
> >
> >
> >
> > Right, but without the crontab you notice it immediately, and not one
> > hour later when you may be away from your keyboard
> i don't see how. mind to explain?

As i explain in my first mail the fact is that samba reload the config
file immediately when it noticed a modification. (i use samba as an
example, other apps may do this)
So without RCS/crontab as soon as i make a mistake i know about it.
With the crontab, the commit may happen while i'm not log in anymore

I can explain why i don't like this kind of automatic , timing based things:
1) i think we should more or less force the admins to write a log
message (svn -m "i added a new vhost") for each commit they do, it
gives valuable information, if the commit is automatic, what will be
the message?
2) we don't really need an auto commit, if he didn't commit, that is
up to him. Maybe he prefers to finish tomorow.
3) this mean that you can't work more than 1 hour on a config file
without being forced to commit? (i hope it's not every plain hour that
it auto commit)

I see why you want this autocommit thing: so a change is never lost in
the "local" repository.
But if he modify a file, this means that he want a result. I don't see
any reason he would log out without commiting and checking that the
change he made , worked. The crontab trick may just make it work
"magically", and he may not understand why.

> >
> > You didn't comment on the "PS1" and "logout" ideas, i think they are
> > still valid with the crontab autocommit, it gives an immediate visual
> > information.
> while the idea might be valid, it would require changes to all shells to check
> for that specific plugin and status. it is a fragile point to touch that i am
> not keep to modify.

I'm willing to implement this, i don't really see the need to
implement it for all shells other than bash/tcsh/zsh.

> Fabio
> --
> I'm going to make him an offer he can't refuse.

Sebastien Estienne

More information about the ubuntu-server mailing list