Sponsored Content
Full Discussion: Chmod Help!
Top Forums UNIX for Dummies Questions & Answers Chmod Help! Post 5144 by Jayathirtha on Wednesday 8th of August 2001 04:29:15 AM
Old 08-08-2001
MySQL

Brian,

Just type
chmod 777 <filename>
at the command prompt. This will do.

Hope this solves your problem buddy...

Jay.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

CHMOD Help!!

Ok, listen.........I was using FTP Works to remove and add some files to a domain server. I messed with chmod button and made it so that no-one could access or their browsers could execute files and 2 or three certain directories. If anyone knows how to use this command and will give me a heads up... (2 Replies)
Discussion started by: jarrell
2 Replies

2. UNIX for Dummies Questions & Answers

chmod

Hi, can anybody help me? i have probable a simple problem about permissions. i have a server and on this server there comes some files from a another server via ftp with a separte user. i would like to modify the files with a awk script but i donīt have the permissions to modify the... (3 Replies)
Discussion started by: scotty
3 Replies

3. UNIX for Dummies Questions & Answers

chmod...

Hey everyone, I was wondering if there was a quicker way to chmod a lot of files than doing what im currently doing. At the moment, im doing chmod 777 *filename* - but I have a lot of files, sub-directories, sub-files etc etc. And at the moment I see I have to chmod every single file... (3 Replies)
Discussion started by: mo0ness
3 Replies

4. UNIX for Dummies Questions & Answers

CHMOD query

Hi peeps, I'm new here, so I hope I'm posting in the right place... If I'm in a particular directory and I run the command 'CHMOD * 777' (or the other way around- I can't remember), am I right in saying it will only change the permissions of all the immediate files and directories and not... (1 Reply)
Discussion started by: jsp_1983
1 Replies

5. UNIX for Dummies Questions & Answers

CHMOD Question

I've always been fascinated by permissions and I have a question. Since the shell isn't a "virtual environment" (like say a web forum, where permissions can be enforced with absolute confidence), what's actually keeping an unauthorized user from viewing a CHMODed file? The read/write routines? Why... (1 Reply)
Discussion started by: froth
1 Replies

6. UNIX for Dummies Questions & Answers

CHMOD problems... Help!

Hey. I was playing somethink with chmods, and then i did chmod -R 755 / :eek: so linux but with errors and sshd not working .... Can some one give me proper chmods or better script that will do it. pls help fast (7 Replies)
Discussion started by: net555
7 Replies

7. Shell Programming and Scripting

help with chmod (files only)

hello, i want to chmod 444 all files in a directory, files in subdirs cannot be chmoded same goes for the subdirs themself. So using: chmod -R 444 /dir/ won't work because it will chmod the directorys and files (together with files in subdirectorys) I figured out how to chmod files... (1 Reply)
Discussion started by: TehOne
1 Replies

8. UNIX for Advanced & Expert Users

chmod question

I have two files,like follows: $ls -l foo bar -rw------- bar -rw-rw-rw- foo Then I execute follow code: chmod("foo",(statbuf.st_mode & ~S_IXGRP) | S_ISGID) chmod("bar",S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH) Then I view the result $ls -l foo bar -rw-r--r-- bar... (1 Reply)
Discussion started by: konvalo
1 Replies

9. UNIX and Linux Applications

What is the difference between chmod in solaris and chmod in Linux?

i think it is the same in both... Iam i right? (1 Reply)
Discussion started by: sumaiya
1 Replies

10. UNIX for Dummies Questions & Answers

chmod

Hi I tried to use chmod in unix to change my file's permission. chmod 701 hello.cgi And it did change my desired file's permission. Yet, the name of the file is changed to hello.cgi* . And therefore I cannot compile it after that. So, I just wondering why there is an extra '*' in the file's... (2 Replies)
Discussion started by: alvin8906
2 Replies
mkdir(1)							   User Commands							  mkdir(1)

NAME
mkdir - make directories SYNOPSIS
/usr/bin/mkdir /usr/bin/mkdir [-m mode] [-p] dir... ksh93 mkdir [-p] [-m mode] dir... DESCRIPTION
/usr/bin/mkdir The mkdir command creates the named directories in mode 777 (possibly altered by the file mode creation mask umask(1)). Standard entries in a directory (for instance, the files ".", for the directory itself, and "..", for its parent) are made automatically. mkdir cannot create these entries by name. Creation of a directory requires write permission in the parent directory. The owner-ID and group-ID of the new directories are set to the process's effective user-ID and group-ID, respectively. mkdir calls the mkdir(2) system call. setgid and mkdir To change the setgid bit on a newly created directory, you must use chmod g+s or chmod g-s after executing mkdir. The setgid bit setting is inherited from the parent directory. ksh93 The mkdir built-in in ksh93 is associated with the /bin and /usr/bin paths. It is invoked when mkdir is executed without a pathname prefix and the pathname search finds a /bin/mkdir or /usr/bin/mkdir executable. mkdir creates one or more directories. By default, the mode of created directories is a=rwx minus the bits set in umask(1). OPTIONS
/usr/bin/mkdir The following options are supported by /usr/bin/mkdir: -m mode This option allows users to specify the mode to be used for new directories. Choices for modes can be found in chmod(1). -p With this option, mkdir creates dir by creating all the non-existing parent directories first. The mode given to intermediate directories is the difference between 777 and the bits set in the file mode creation mask. The difference, however, must be at least 300 (write and execute permission for the user). ksh93 The following options are supported by the mkdir built-in in ksh93: -m mode Set the mode of created directories to mode. mode is symbolic or octal mode as in chmod(1). Relative modes assume an initial --mode=mode mode of a=rwx. -p Create any missing intermediate pathname components. For each dir operand that does not name an existing directory, effects --parents equivalent to those caused by the following command shall occur: mkdir -p -m $(umask -S),u+wx $(dirname dir) && mkdir [-m mode] dir Where the -m mode option represents that option supplied to the original invocation of mkdir, if any. Each dir operand that names an existing directory is ignored without error. OPERANDS
The following operand is supported: dir A path name of a directory to be created. USAGE
See largefile(5) for the description of the behavior of mkdir when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes). EXAMPLES
Example 1 Using mkdir The following example: example% mkdir -p ltr/jd/jan creates the subdirectory structure ltr/jd/jan. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of mkdir: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 All the specified directories were created successfully or the -p option was specified and all the specified directories now exist. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/mkdir +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ ksh93 +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ The ksh93 built-in binding to /bin and /usr/bin is Volatile. The built-in interfaces are Uncommitted. SEE ALSO
chmod(1), ksh93(1), rm(1), sh(1), umask(1), Intro(2), mkdir(2), attributes(5), environ(5), largefile(5), standards(5) SunOS 5.11 2 Nov 2007 mkdir(1)
All times are GMT -4. The time now is 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy