Re: backup manifests and contemporaneous buildfarm failures
| От | Fabien COELHO |
|---|---|
| Тема | Re: backup manifests and contemporaneous buildfarm failures |
| Дата | |
| Msg-id | alpine.DEB.2.21.2004060714030.16227@pseudo обсуждение исходный текст |
| Ответ на | Re: backup manifests and contemporaneous buildfarm failures (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: backup manifests and contemporaneous buildfarm failures
|
| Список | pgsql-hackers |
Hello,
>> Do I need to precede those with some recursive chmod commands? Perhaps
>> the client should refuse to run if there is still something left after
>> these.
>
> I think the latter would be a very good idea, just so that this sort of
> failure is less obscure. Not sure about whether a recursive chmod is
> really going to be worth the cycles. (On the other hand, the normal
> case should be that there's nothing there anyway, so maybe it's not
> going to be costly.)
Could it be a two-stage process to minimize cost but still be resilient?
rmtree
if (-d $DIR) {
emit warning
chmodtree
rmtree again
if (-d $DIR)
emit error
}
--
Fabien.
В списке pgsql-hackers по дате отправления: