Good luck with your nightmare.
if i would be in his case i would first not touch it and then slowly
analyze EVERYTHING that is used on that system, and ask users how exactly
they use it (i mean shared folders etc).
Then i will step by step fix things to proper state, waiting for
complaints
> I have inherited a problem that is no cause for envy, the previous
> administrators had no idea what they were doing, so problems with a
> permission denied would be solved by chown -R 777 /whatever! Needless to
> say, it's a mess, and ofcourse everything is "critical" there is no room
> for inte
l 2012 10:12:05 +0200 (CEST)
> > Subject: Re: Help solving the sysadm's nightmare
> >
>
> [[ sarcastic comment with no useful value removed ]]
>
> > > it's a mess, and ofcourse everything is "critical" there is no room for
> > > interru
> From: Wojciech Puchar
> Date: Thu, 19 Jul 2012 10:12:05 +0200 (CEST)
> Subject: Re: Help solving the sysadm's nightmare
>
[[ sarcastic comment with no useful value removed ]]
> > it's a mess, and ofcourse everything is "critical" there is no room for
&g
On Thu, 19 Jul 2012 08:55:29 +0200, Erik Nørgaard wrote:
> Now, I have no idea which processes actually require access to those
> files, what privileges these processes run with and which files are
> actually executable or just plain files.
For differentiating "files' nature", use "file "
to ide
administrators had no idea what they were doing, so problems with a
permission denied would be solved by chown -R 777 /whatever! Needless to say,
great.
rm -rf /whatever would be even better!
it's a mess, and ofcourse everything is "critical" there is no room for
interruption of service.
Now
On 19/07/2012 07:55, Erik Nørgaard wrote:
> So, how can I
>
> - determine if files are actually unix executables or just plain files
> (or windows executables)?
file(1) should help.
> - determine which users actually need read or write access to these files?
This is in most cases entirely a loc
