我想写Ubuntu的类似于"批处理文件"(一个shell脚本)。但我不知道如何使用chmod +x filename
命令来使脚本能够被运行。我也不知道该在哪里使用它。
在一个文件(你的脚本)上的 "chmod +x "只意味着,你将使它可以执行。在你的脚本上点击右键,选择属性 -> 权限 -> 允许将文件作为程序执行,你会得到与终端命令完全相同的结果。
如果你想改变权限的文件位于系统目录中,你可能需要成为 "root",像这样。(小心,在使用sudo
命令时)
sudo chmod +x /usr/share/testfolder/aFile
另外,不清楚你到底想在这里存档什么。请编辑你的问题,并就实际问题提供更多的细节!
你也可以参考这个问题,了解更多信息。chmod u+x'与'chmod +x
在终端窗口中输入man chmod
(Ctrl+Alt+T),你将得到以下输出。
名称: chmod - 更改文件模式位
SYNOPSIS
chmod [OPTION]... MODE[,MODE]... FILE...
chmod [OPTION]... OCTAL-MODE FILE...
chmod [OPTION]... --reference=RFILE FILE...
描述
This manual page documents the GNU version of chmod. chmod changes the
file mode bits of each given file according to mode, which can be either
a symbolic representation of changes to make, or an octal number repre‐
senting the bit pattern for the new mode bits.
The format of a symbolic mode is [ugoa...][[+-=][perms...]...], where
perms is either zero or more letters from the set rwxXst, or a single
letter from the set ugo. Multiple symbolic modes can be given, sepa‐
rated by commas.
A combination of the letters ugoa controls which users' access to the
file will be changed: the user who owns it (u), other users in the
file's group (g), other users not in the file's group (o), or all users
(a). If none of these are given, the effect is as if a were given, but
bits that are set in the umask are not affected.
The operator + causes the selected file mode bits to be added to the
existing file mode bits of each file; - causes them to be removed; and =
causes them to be added and causes unmentioned bits to be removed except
that a directory's unmentioned set user and group ID bits are not
affected.
The letters rwxXst select file mode bits for the affected users: read
(r), write (w), execute (or search for directories) (x), execute/search
only if the file is a directory or already has execute permission for
some user (X), set user or group ID on execution (s), restricted dele‐
tion flag or sticky bit (t). Instead of one or more of these letters,
you can specify exactly one of the letters ugo: the permissions granted
to the user who owns the file (u), the permissions granted to other
users who are members of the file's group (g), and the permissions
granted to users that are in neither of the two preceding categories
(o).
A numeric mode is from one to four octal digits (0-7), derived by adding
up the bits with values 4, 2, and 1. Omitted digits are assumed to be
leading zeros. The first digit selects the set user ID (4) and set
group ID (2) and restricted deletion or sticky (1) attributes. The sec‐
ond digit selects permissions for the user who owns the file: read (4),
write (2), and execute (1); the third selects permissions for other
users in the file's group, with the same values; and the fourth for
other users not in the file's group, with the same values.
chmod never changes the permissions of symbolic links; the chmod system
call cannot change their permissions. This is not a problem since the
permissions of symbolic links are never used. However, for each sym‐
bolic link listed on the command line, chmod changes the permissions of
the pointed-to file. In contrast, chmod ignores symbolic links encoun‐
tered during recursive directory traversals.
setuid和setgid位
chmod clears the set-group-ID bit of a regular file if the file's group
ID does not match the user's effective group ID or one of the user's
supplementary group IDs, unless the user has appropriate privileges.
Additional restrictions may cause the set-user-ID and set-group-ID bits
of MODE or RFILE to be ignored. This behavior depends on the policy and
functionality of the underlying chmod system call. When in doubt, check
the underlying system behavior.
OPTIONS
Change the mode of each FILE to MODE.
-c, --changes
like verbose but report only when a change is made
--no-preserve-root
do not treat `/' specially (the default)
--preserve-root
fail to operate recursively on `/'
-f, --silent, --quiet
suppress most error messages
-v, --verbose
output a diagnostic for every file processed
--reference=RFILE
use RFILE's mode instead of MODE values
-R, --recursive
change files and directories recursively
--help display this help and exit
--version
output version information and exit
Each MODE is of the form `[ugoa]*([-+=]([rwxXst]*|[ugo]))+'.
在Linux下,批处理文件和shell脚本是两个含义相同的术语。不过,脚本这个术语更经常被使用。
最简单的shell脚本文件只包含你在命令行上输入的命令(也就是Bash命令解释器)。理论上,你甚至可以用任何你喜欢的语言(并且有一个解释器)来代替解释器。为了更加明确,建议你在第一行开始时使用
#!/bin/sh`(如果你想在传统系统中获得最大的可移植性)
或
#!/bin/bash
(如果你想要一些额外的功能,你今天可能不关心这些)。
在这一行之后输入你的命令,每行一个。还有很多超出本问题范围的额外结构,见man bash
或http://www.tldp.org/LDP/Bash-Beginners-Guide/Bash-Beginners-Guide.pdf(初学者)或http://www.tldp.org/LDP/abs/abs-guide.pdf(更高级的问题)。
要实际运行你的脚本,有两个要求。首先,解释器进程需要读取文件,其次它要检查文件是否被标记为可执行文件。为了方便起见,能够写入你的脚本也是很有用的(这样你就可以在需要时进行修改或修复)。
假设你希望团队成员和其他人员也能运行(并看到)你的脚本,但你不希望他们对其进行操作,那么结合
a+x
或+x
,因为a
是默认的)。a+r
或+r
,因为a
还是默认的)。u=w
)通常是你的文件权限的合理值。你可以输入单项行动的串联,用逗号分开。
虽然这种动作语言非常吸引人(注意+
和=
运算符的区别,它们导致不同的结果,取决于你改变它们之前的权限设置),但它们的输入很繁琐。
由于所有的操作都创建了内部应用的位掩码,你也可以直接输入位掩码(详见man chmod
)。
对于shell脚本来说,chmod 755 myscript.sh在至少95%的情况下是最有意义的。