At 2004-04-09T05:41:33Z, "dave" <[EMAIL PROTECTED]> writes:
> I've got a problem, a directory area has the wrong permissions, occurred
> from a dump restore.
Out of curiosity, how is it that your permissions were different after the
restore than before?
--
Kirk Strauser
"94 outdated ports on th
On Fri, Apr 09, 2004 at 02:03:51AM -0700, Cory Petkovsek wrote:
> On Fri, Apr 09, 2004 at 08:47:07AM +0200, Uwe Doering wrote:
> > >cd $topdir
> > >find . -type d | xargs chmod 755
> >
> > In case (potentially) untrusted users have had write permission in this
> > directory tree in the past, a sa
Cory Petkovsek wrote:
On Fri, Apr 09, 2004 at 08:47:07AM +0200, Uwe Doering wrote:
cd $topdir
find . -type d | xargs chmod 755
In case (potentially) untrusted users have had write permission in this
directory tree in the past, a safer alternative would be
find /path/to/tree/root -type d -print0
On Fri, Apr 09, 2004 at 08:47:07AM +0200, Uwe Doering wrote:
> >cd $topdir
> >find . -type d | xargs chmod 755
>
> In case (potentially) untrusted users have had write permission in this
> directory tree in the past, a safer alternative would be
>
> find /path/to/tree/root -type d -print0 | xa
Bill Campbell wrote:
On Fri, Apr 09, 2004, dave wrote:
Hello,
I've got a problem, a directory area has the wrong permissions, occurred
from a dump restore. Now my user's can't get to the files within the area. I
could go around and do chmod permissions directoryname, but i was wondering
if the
On Fri, Apr 09, 2004, dave wrote:
>Hello,
>I've got a problem, a directory area has the wrong permissions, occurred
>from a dump restore. Now my user's can't get to the files within the area. I
>could go around and do chmod permissions directoryname, but i was wondering
>if there was a perl or
