irectory.
- -Tom
- -Original Message-
From: Richard S. Crawford [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 5:14 PM
To: [EMAIL PROTECTED]
Subject: RE: Directory permissions
You shouldn't have to. Setting chmod 777 on the directory should do
it
just fine.
On the other hand
[mailto:[EMAIL PROTECTED]]
On Behalf Of Richard S. Crawford
Sent: Tuesday, January 21, 2003 2:14 PM
To: [EMAIL PROTECTED]
Subject: RE: Directory permissions
You shouldn't have to. Setting chmod 777 on the directory should do it
just fine.
On the other hand, Bret might be right as well.
Crawford [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 21, 2003 4:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Directory permissions
>
>
> # mkdir /openDirectory
> # chmod 777 -R /openDirectory
>
> is one way to do it, but probably kind of clunky and insecure. It&#
Richard S. Crawford [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 4:47 PM
To: [EMAIL PROTECTED]
Subject: Re: Directory permissions
# mkdir /openDirectory
# chmod 777 -R /openDirectory
is one way to do it, but probably kind of clunky and insecure. It's
worked on my system.
You mig
# mkdir /openDirectory
# chmod 777 -R /openDirectory
is one way to do it, but probably kind of clunky and insecure. It's
worked on my system.
You might also want to look into the umask command.
On Tue, 2003-01-21 at 13:16, Burke, Thomas G. wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: S
On Tue, 2003-01-21 at 15:16, Burke, Thomas G. wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hey gang,
>
> I'd leike to set up a directory such that anytime a file is written
> to that directory, it is created chmod 777, regardless of who creates
> it, or how it is created. A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey gang,
I'd leike to set up a directory such that anytime a file is written
to that directory, it is created chmod 777, regardless of who creates
it, or how it is created. Anyone know how to do this?
Thanks,
Tom
--
On Wed, Sep 04, 2002 at 09:19:16AM -0400, Timothy Writer wrote:
> I recommend using find in combination with xargs instead of -exec. Like
> this:
>
> find -type f -print | xargs chmod 644
> find -type d -print | xargs chmod 755
I agree about xargs, but use the NUL options:
U
ssage-
> From: Gordon McDowall [mailto:[EMAIL PROTECTED]]
> Sent: 04 September 2002 11:18
> To: '[EMAIL PROTECTED]'
> Subject: file - directory permissions
>
>
> Hi
>
> We run a few virtual web servers and often get people who have changed the
> permissions
Thanks for that Phil, my brain seems to be out to lunch today :o)
-Original Message-
From: Skuse, Phil [mailto:[EMAIL PROTECTED]]
Sent: 04 September 2002 11:28
To: '[EMAIL PROTECTED]'
Subject: RE: file - directory permissions
how about
find -type f -exec chmod 644 {} \;
fin
how about
find -type f -exec chmod 644 {} \;
find -type d -exec chmod 755 {} \;
-Original Message-
From: Gordon McDowall [mailto:[EMAIL PROTECTED]]
Sent: 04 September 2002 11:18
To: '[EMAIL PROTECTED]'
Subject: file - directory permissions
Hi
We run a few virtual web s
Hi
We run a few virtual web servers and often get people who have changed the
permissions of many of the directories and files within their website root
directory. Has anyone ever seen/written a script that would reset the
permissions on everything below their root directory ie files to 644 but
On Sat, 2002-07-06 at 02:44, Cameron Simpson wrote:
> On 02:12 06 Jul 2002, Jay Daniels <[EMAIL PROTECTED]> wrote:
> | I am also interested in this topic. According to the man page chroot
> | would work something like this as users shell but I can't get it work
> | even though I copied /bin/bash t
On Fri, 5 Jul 2002, Ted Gervais wrote:
>
> What does one have to do, to keep users that enter your system, to stay in
> their own directories. People telnet in or ssh in and look around and was
> wondering if there is a way to stop that. Maybe set the permissions or
> something so they have
On 02:12 06 Jul 2002, Jay Daniels <[EMAIL PROTECTED]> wrote:
| I am also interested in this topic. According to the man page chroot
| would work something like this as users shell but I can't get it work
| even though I copied /bin/bash to /home/login/bin
|
| chroot /home/login /home/login/bin/ba
On Fri, 2002-07-05 at 23:46, Cameron Simpson wrote:
> On 15:58 05 Jul 2002, Ted Gervais <[EMAIL PROTECTED]> wrote:
> | What does one have to do, to keep users that enter your system, to stay in
> | their own directories. People telnet in or ssh in and look around and was
> | wondering if there
On 15:58 05 Jul 2002, Ted Gervais <[EMAIL PROTECTED]> wrote:
| What does one have to do, to keep users that enter your system, to stay in
| their own directories. People telnet in or ssh in and look around and was
| wondering if there is a way to stop that. Maybe set the permissions or
| somet
What does one have to do, to keep users that enter your system, to stay in
their own directories. People telnet in or ssh in and look around and was
wondering if there is a way to stop that. Maybe set the permissions or
something so they have to remain in their own home directory??
Is that
Chris Montgomery wrote:
>
> Thanks for the comeback, Andreas. Comments inline below.
>
You're welcome.
> > Generally though it's better to be root when installing things.
> >
>
> Since I am the only user on this machine, would this really matter? My
> impression was that if programs are goin
Thanks for the comeback, Andreas. Comments inline below.
On Tue, 08 Jan 2002 12:46:09 +0100
Andreas Berglund <[EMAIL PROTECTED]> wrote:
>
> If you have access to the root account then just become root and type
> "chown your_account_name /usr/local". With the chown command the owner
> of a file
To write to your Windows directory (assuming it is vfat),
add a line like this to your /etc/fstab:
/dev/hda1 /mnt/win vfatnoauto,users,owner 0 0
and mount the partition while logged in as your normal user
account (mount /mnt/win). Then, the files will be owned by you.
This give
Chris Montgomery wrote:
>
> Newbie alert...
>
> I am trying to install the StarOffice 6 beta into my /usr/local directory,
> as a user (not root). I cannot create a subdirectory
> (/usr/local/staroffice6.0) since /usr/local is owned by root. How can I
> change this to my user account?
If you ha
ED]
> Date: Mon, 7 Jan 2002 15:25:44 -0600
> To: [EMAIL PROTECTED]
> Subject: Changing Directory Permissions
>
> Newbie alert...
>
> I am trying to install the StarOffice 6 beta into my /usr/local directory,
> as a user (not root). I cannot create a subdirectory
> (/usr/local/
Newbie alert...
I am trying to install the StarOffice 6 beta into my /usr/local directory,
as a user (not root). I cannot create a subdirectory
(/usr/local/staroffice6.0) since /usr/local is owned by root. How can I
change this to my user account? I have the same question about being able
to writ
- Original Message -
From: Jeff Graves <[EMAIL PROTECTED]>
To: Redhat <[EMAIL PROTECTED]>
Sent: Friday, April 13, 2001 3:06 PM
Subject: File and Directory Permissions
: Hi Guys,
:
: It's been a while, but I just threw together a Redhat 7.0 FTP server and
: have a ve
> It's been a while, but I just threw together a Redhat 7.0 FTP server and
> have a very basic question which has stumped me. Forgive me for what I am
> about to ask, but someone knows how to do this:
Another route is if you plan to use WU-FTPD. It also has powerful
configuration features.
Mar
Hi Jeff,
> I have a group of customers, each has unique username and password, all
> belong to the same group.
> They can also see the root which will contain all the other
> directories but access will be denied because of the 700 permissions. Now, I
> wish to create a user, cal
Hi Guys,
It's been a while, but I just threw together a Redhat 7.0 FTP server and
have a very basic question which has stumped me. Forgive me for what I am
about to ask, but someone knows how to do this:
I have a group of customers, each has unique username and password, all
belo
28 matches
Mail list logo
