blocks|key|854893|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|-4|4|5|6|B|7|@]|8|@]|9|$]]]|A|$]]

You likely shouldn't do that. You can probably achieve your goal in way that does not involve writing one script that generates another script that you will later modify and run; see below. But if you really want to do it, and you want to do it with code that closely resembles what you've shown, then steeldriver is right that a <a href="https://www.gnu.org/software/bash/manual/bash.html#Here-Documents" rel="nofollow noreferrer">here document</a> is a workable way.

<a href="https://askubuntu.com/a/1157644/22949">The way steeldriver uses a here document</a> is fine; here's another, whose code is a bit simpler. (I'm presenting it mainly for the opportunity to explain the meaning of each part of its syntax, not out of the belief that this approach is superior.)



<pre class="lang-bash prettyprint-override"><code>#!/bin/bash
cat &gt;/usr/local/sbin/adduser.local &lt;&lt;'EOF'
#!/bin/bash
lastuser="$(grep home /etc/passwd | cut -d: -f 1 | tail -1)"
EOF
</code></pre>

Replace <code>/usr/local/sbin/adduser.local</code> with whatever name you want for the second script, if it is different. Then simply run the script as root, for example with <code>sudo</code>. The entire point of this script is to create a file in a location only root has write access to, so it is itself the sort of command that makes sense to run as root with <code>sudo</code>. When you have a script in which every command starts with <code>sudo</code> (especially if it's a one-command script), that often suggests that the script shouldn't use <code>sudo</code> inside of it at all but should instead just be run with <code>sudo</code>.

Depending on how you're running the generated script, you may need to give it execute permissions, which you can do with <code><a href="http://manpages.ubuntu.com/manpages/bionic/en/man1/chmod.1.html" rel="nofollow noreferrer">chmod</a> +x</code>. (That applies to <a href="https://askubuntu.com/a/1157644/22949">steeldriver's way</a>, as well.) If the file already exists and has execute permissions, and you're overwriting it, then you don't need to run <code>chmod</code>.

The way the command shown above works is that:

<ul>
<li>When <a href="http://manpages.ubuntu.com/manpages/bionic/en/man1/cat.1.html" rel="nofollow noreferrer"><code>cat</code></a> is run with no filename arguments (as is the case here), it simply copies its input to its output.</li>
<li><code>cat</code>'s output is redirected to the file <code>/usr/local/sbin/adduser.local</code> by the <a href="https://www.gnu.org/software/bash/manual/bash.html#Redirecting-Output" rel="nofollow noreferrer">output redirection</a> operator <code>&gt;</code>. I've used the <code>&gt;</code> operator, which overwrites, even though you were using <code>&gt;&gt;</code>, which appends. I'm doing this because I assume you want to overwrite that file, because the text you're placing in it starts with a <a href="https://en.wikipedia.org/wiki/Shebang_(Unix)" rel="nofollow noreferrer">hashbang</a>, which doesn't usually make sense except <a href="https://askubuntu.com/questions/238002/is-bin-sh-read-by-the-interpreter">at the beginning of a file</a>.</li>
<li><code>cat</code>'s input is taken from the text that appears on the following line, up to but not not including any of the line that begins with <code>EOF</code>, stipulated by the <a href="https://www.gnu.org/software/bash/manual/bash.html#Here-Documents" rel="nofollow noreferrer">here document</a> notation <code>&lt;&lt;</code>.</li>
<li>Quoting <code>EOF</code> after <code>&lt;&lt;</code> -- that is, writing <code>&lt;&lt;'EOF'</code> rather than <code>&lt;&lt;EOF</code> -- suppresses <a href="https://www.gnu.org/software/bash/manual/bash.html#Shell-Expansions" rel="nofollow noreferrer">expansions</a> in the body of the here document, so that none of the characters in the bash code there are treated specially by the shell running the first script.</li>
</ul>

Using a here document eliminates difficulties associated with quotes that are nested inside other quotes. If you ever need the body of a here document to contain <code>EOF</code>, that's fine, because although <code>EOF</code> is one of the popular choices of word, it's not special at all. You can use whatever word you like. Just use it both after <code>&lt;&lt;</code> and at the beginning of a line that appears by itself after the last line you wish to provide as input--just as <code>EOF</code> is used above.

<hr>

There are several reasons you should probably not actually do that (nor use any <code>echo</code>-based method) in the situation you appear to be describing.

First, if your goal is to allow non-root users to install updates, editing <code>sudoers</code> might not be the best way to achieve that. There are other approaches; for example, <a href="https://askubuntu.com/questions/41859/how-to-automatically-install-updates-by-a-desktop-user">you can schedule updates for automatic unattended installation or let non-root users use the update manager</a> and you may be interested in <a href="https://askubuntu.com/a/258/22949">this technique or some variation on it</a>. I'm not sure quite what your requirements are, but you might want to ask about <a href="https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem">whatever specific problem</a> you're trying to solve.

Second, if you do end up editing <code>/etc/sudoers</code>, it's usually bad to do so in a way that does not involve automatically checking for syntax errors and rejecting modifications that introduce them. (It is also often better to create or edit a sudoers file in the <code>/etc/sudoers.d</code> directory rather than modifying the main sudoers file <code>/etc/sudoers</code>, but the same cautions and considerations apply.) When you manually edit a sudoers file with the <code>visudo</code> command, such checks are performed; the file you're editing is not a real sudoers file, but is instead a temporary file that is checked and only copied over to a real sudoers file after passing syntax checks.

The slightest syntax error in any sudoers file causes sudo to refuse to allow anyone to perform actions as root! <a href="https://askubuntu.com/a/73872/22949">This is often easy to fix</a>, but if the reason you're not using a Polkit-based approach is that this is a server system without Polkit, then it's a bit harder. If you must edit a sudoers file not through <code>visudo</code>, you can take the precautionary measure of opening a root shell, separate from the shell in which you're running the commands that modify your configuration, such as by running <code>sudo -i</code>. Once started, this will remain usable, for as long as it is running, even if <code>sudo</code> is broken.

You can actually use <code>visudo</code> to check the syntactic correctness of automated, scripted modifications to sudoers files! This is possible because it accepts any command as the text editor to use to edit the file; this can be customized for a single run of <code>visudo</code> using the <code>SUDO_EDITOR</code> environment variable, and you can write a script that behaves as that editor but is automated and requires no interactions (except perhaps in the event that it produces a syntax error that <code>visudo</code> blocks). I'd consider the details beyond the scope of this answer; if you want help doing something like that, you could ask another question about it.

Third, it looks like you're planning to add several (perhaps many) entries to a sudoers file, for individual users. If so, you should consider adding a single entry for a group and adding the users to the group. This is the approach used to allow administrators on an Ubuntu system to run arbitrary commands as root with <code>sudo</code>; such users are members of the <code>sudo</code> group, which <code>/etc/sudoers</code> has an entry for. You can create other groups and give them other permissions, which can be more restrictive than the ability the <code>sudo</code> group has to run arbitrary commands.

Fourth, even if you do want to follow the approach you're taking, there are better ways than having one script embed a fragment that it uses to seed other scripts that you manually modify. The two approaches I suspect you might find most useful are:

<ul>
<li>You can put <code>lastuser="$(grep home /etc/passwd | cut -d: -f 1 | tail -1)"</code> in a file, which need not be executable nor start with a <code>#!</code> hashbang line, and then source that file in whatever scripts are going to use <code>lastuser</code>, by having those scripts contain the command <code>. lastuser.sh</code> (or <code>source lastuser.sh</code>, which is equivalent in bash), where <code>lastuser.sh</code> is the name of the file that contains the command. The <code>lastuser</code> variable gets defined at the time the <code>. lastuser.sh</code> command runs, so it will still always depend on the current state of <code>/etc/passwd</code>.</li>
<li>If you really do want one script to create another, then rather than embedding the code that will be copied into the first script, you can make a master file that contains it have the first script just copy that file to the desired location. You could do the copying with <a href="http://manpages.ubuntu.com/manpages/bionic/en/man1/cp.1.html" rel="nofollow noreferrer"><code>cp</code></a> or <a href="http://manpages.ubuntu.com/manpages/bionic/en/man1/install.1.html" rel="nofollow noreferrer"><code>install</code></a>.</li>
</ul>

blocks|key|6728542|text|使用这里的文档，确保引用分隔符单词，以便shell不会展开正文中的任何内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6728543|#!/bin/bash++++

cat+<<+'EOF'+%7C+sudo+tee+-a+/usr/local/sbin/adduser.local
#!/bin/bash
lastuser="$(grep+home+/etc/passwd+%7C+cut+-d:+-f+1+%7C+tail+-1)"
EOF|code-block|syntax|javascript|6728544|tee的使用是因为sudo+echo+"..."+>>+somefile没有做你认为它做的事情--参见如何解决在Bash中使用带重定向的sudo时“拒绝权限”的问题？|offset|length|style|CODE|entityMap|0|LINK|mutability|MUTABLE|url|https://askubuntu.com/questions/230476/how-to-solve-permission-denied-when-using-sudo-with-redirection-in-bash^0|0|0|0|3|9|R|1F|W|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@$I|W|J|X|K|L]|$I|Y|J|Z|K|L]]|9|@$I|10|J|11|1|12]]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Use a here document, making sure to quote the delimiter word so that the shell does not expand anything in the body:

<pre><code>#!/bin/bash 

cat &lt;&lt; 'EOF' | sudo tee -a /usr/local/sbin/adduser.local
#!/bin/bash
lastuser="$(grep home /etc/passwd | cut -d: -f 1 | tail -1)"
EOF
</code></pre>

The use of <code>tee</code> is because <code>sudo echo "..." &gt;&gt; somefile</code> doesn't do what you think it does - see <a href="https://askubuntu.com/questions/230476/how-to-solve-permission-denied-when-using-sudo-with-redirection-in-bash">How to solve “permission denied” when using sudo with redirection in Bash?</a>

I want to make echo from one script to another script, but I don't want to get the output of the command because I want to use this command in another script, I need to create a script that creates the adduser.local script for me.

The first script is:

<pre><code>#!/bin/bash
sudo echo "
#!/bin/bash
'lastuser="$(grep home /etc/passwd | cut -d: -f 1 | tail -1)"' " &gt;&gt;
/usr/local/sbin/adduser.local
</code></pre>

and what I get from /usr/local/sbin/adduser.local is the output of the command, and I want to copy the command as is because I don't want to get the output in the first script I want to get the output in the second script.
So I need to know how to use the echo right that the first script drops the command as is to adduser.local.

The adduser.local script needs to look like this after the first run

<pre><code>#!/bin/bash
lastuser="$(grep home /etc/passwd | cut -d: -f 1 | tail -1)"
#and now i can use the $lastuser in this script
echo " '$lastuser' ALL = !/usr/bin/apt-get update " &gt;&gt; /etc/sudoers
</code></pre>

How to echo commands to other file

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我想从一个脚本回显到另一个脚本，但是我不想获得命令的输出，因为我想在另一个脚本中使用这个命令，我需要创建一个为我创建adduser.local脚本的脚本。第一个脚本是：#!/bin/bashsudo echo "#!/bin/bash'lastuser="$(grep home /etc/passwd | cut -d: -f 1 | tail -1)"' " >>/usr/local/sbin/

问如何将命令回显到其他文件
EN

回答 2

Ask Ubuntu用户

Ask Ubuntu用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将命令回显到其他文件EN

回答 2

Ask Ubuntu用户

Ask Ubuntu用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将命令回显到其他文件
EN