inline.... On Tue, Aug 12, 2008 at 11:41 PM, Chris Louden <[email protected]>wrote:
> On Tue, Aug 12, 2008 at 10:15 PM, Dante Lanznaster <[email protected]> > wrote: > > you might try using quotes whenever referencing these folders with > special > > characters... in Windows itself there's no problem with ! @ # $ % ^ & ( ) > > but some of these might influence in a linux command... > > Yes, but that is not the issue/question at hand. While I do not claim > to be a CLI expert I know to use quotes for complex names in my own > scripting. > > The question is - could complex folder names cause issues with > permissions? Specifically when files are accessed/created via Samba. > When the system attempts to write the file attributes could this fail > due to a complex directory name? not that I know of > > > Windows is able to inherit permissions from parent "folders" to sub > "folders". This is not the case with Linux. "Directories" can be set > to have the group ID as sticky. When this is applied files in the > "directory" will receive the same group ID as the directory they are > in. If there are further sub directories the group ID for those sub > directories would also need to be set as sticky for files in those sub > directories to retain that directories group ID. > > # chmod -R g+s directoryname should do this to a directory and its sub > directories. As files in each applicable directory are > modified/created the files should retain the group ID that is applied > to the directory the file resides in. Right? right. > > > > > > > On Tue, Aug 12, 2008 at 7:26 PM, Chris Louden <[email protected]> > wrote: > >> > >> On Tue, Aug 12, 2008 at 7:06 PM, Michael Sokolov > >> <[email protected]> wrote: > >> > Chris Louden <[email protected]> wrote: > >> > > >> >> Anyone ever had issues with permissions on folders that contain (#) > >> >> (@) or( ,) in the name? > >> > > >> > Ahmm, Linux (just like UNIX) doesn't have folders, it has directories. > >> > > >> > As far as characters in file and directory names go: dunno about > Linux, > >> > but in UNIX the name of a file (any file, be it a regular file, a > >> > directory, a symlink, a block or character device node or a socket) > may > >> > be up to 255 characters in length and may contain ANY 7-bit ASCII > >> > characters except NUL and '/'. > >> > > >> > Permissions have absolutely nothing to do with it: the name and the > >> > permission bits are completely orthogonal. Furthermore, the > permission > >> > bits are part of the i-node and there may be more than one filename > (in > >> > the same or in different directories) referring to the same i-node. > >> > > >> > MS > >> > >> to clarify. I appear to be having issues with new files being created > >> via SMB and not receiving the appropriate permissions and membership > >> based on the sticky settings. The "directories" that this occurs in > >> have complex names that _could_ potentially have issues with scripts > >> due to the use of # , @ and other characters. Although > >> troubleshooting is not complete. > >> > >> > _______________________________________________ > >> > LinuxUsers mailing list > >> > [email protected] > >> > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers > >> > > >> > >> > >> > >> -- > >> -Chris > >> _______________________________________________ > >> LinuxUsers mailing list > >> [email protected] > >> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers > > > > > > _______________________________________________ > > LinuxUsers mailing list > > [email protected] > > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers > > > > > > > > -- > -Chris > _______________________________________________ > LinuxUsers mailing list > [email protected] > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers >
