bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't chmod file


From: Bob Proulx
Subject: Re: Can't chmod file
Date: Mon, 15 Jun 2009 12:38:57 -0600
User-agent: Mutt/1.5.18 (2008-05-17)

Derrick,

Please keep the discussion on the mailing list.  Use the "list-reply"
feature of your mailer.  Or if your mailer doesn't have that then use
the "group follow-up" or "reply-to-all" feature.  This way everyone
can participate in the discussion and correct my mistakes.  Also
others who look for this later can learn from the discussion in the
mail archives.

Derrick Manor wrote:
> yes. tells me that it can't find directory/file when i clearly have
> path typed in there.

It may be clear to you but to be clear to us you need to show us your
exact commands.  Otherwise I am biased to believe what the command is
telling you.  If the program says that the file isn't there then I
believe that the file isn't there.

> i was able to do it successfully yesterday adn the server changed
> permissions back to default and now can't chown with Putty. A major
> bug somewhere.

So far I don't yet see a bug yet.  Having much experience working with
these types of issues with web servers most of the time it turns out
to be simple confusion.

In other words, don't just say that there is a bug.  Instead please
show us your problem.  Show it to us exactly.

Also putty doesn't have anything to do with changing the mode of a
file.  Putty is a terminal emulator with a built in ssh client.  It
doesn't change the mode of files.  Putty is providing you with a
terminal connected to your server.  On your server you are running a
command line shell and executing commands.  The chmod command there is
telling you that the file you are asking it to change doesn't exist.
I believe the command's output that the file does not exist.

Additionally the entire topic of file modes and file ownership and
access capabilities when dealing with a remote web server isn't
completely simple.  Using history as a predictor I would guess that
what you are doing is trying to open up permissions because the web
server is running as a different user than installer.  It may be
possible that you really want to change the ownership of the file
instead of the permission.  Again, we don't know anything about what
are you doing.

Bob




reply via email to

[Prev in Thread] Current Thread [Next in Thread]