All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: linux-newbie@vger.kernel.org
Subject: Re: 2 questions: 1. ssh permissions to 777 and 2. recursively change all directories/files to 777
Date: Fri, 10 Dec 2004 16:05:11 -0500	[thread overview]
Message-ID: <41BA0F87.50806@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0412101448570.4138-100000@hestia>


> 
>>Question 2:
>>Try the following:
>>
>>-----------------------------------[cut]--------------------------------------------
>>-----------------------------------[cut]--------------------------------------------
>>
>>I use this to fix permissions on a Samba box - you will have to modify or drop the 
>>chown line to leave the ownership properties alone.
> 
> 
> Why not adding a special group to your /etc/group or setting a default
> mask in your smb.conf ? That's what these programs, files are for..
> That would eliminate the need of your script.. And is one cronjob
> less.. One process less, memory less, cpu cycles less.. etc..
> 
> J.
> 

Sorry - one bit of info I left out.  The same filesystem is also exported via NFS.

I don't control all the *nix boxes that connect to it, and the Slackware / Solaris 
/ Red Hat mix makes for some... err... interesting file permission issues.  UID's 
don't matter (it's a media repository), and I only run this after some mistake was 
made on the *nix side (i. e. ripping a CD as root, changing out of group users and 
copying files on the server, etc.).  Samba tends to be pretty well-behaved.  It's 
the NFS stuff that causes problems.

> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-12-10 21:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 17:29 Remote X Little, Chris
2004-04-14 12:01 ` Juan Facundo Suárez
2004-10-13 18:43 ` Setting permissions via SSH upload to 777 Eve Atley
2004-10-13 19:23   ` Ray Olszewski
2004-12-09 21:11 ` 2 questions: 1. ssh permissions to 777 and 2. recursively change all directories/files " Eve Atley
2004-12-09 21:12   ` Jeff Woods
2004-12-09 21:57   ` Ray Olszewski
2004-12-09 22:35     ` Simon Valiquette
2004-12-10 10:37   ` Jim Nelson
2004-12-10 13:53     ` J.
2004-12-10 21:05       ` Jim Nelson [this message]
2004-12-10 13:48   ` J.
2004-12-13 21:54   ` Stephen Samuel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41BA0F87.50806@verizon.net \
    --to=james4765@verizon.net \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.