blocks|key|505642|text|您需要做的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|505643|start-stop-daemon+--start+--quiet+--chuid+$DAEMONUSER++++\
++++--make-pidfile+--pidfile+$PIDFILE+--background+++++++\
++++--exec+/bin/bash+--+-c+"$DAEMON+$DAEMON_ARGS+>+/var/log/some.log+2>&1"|code-block|syntax|javascript|505644|另外，如果您使用--chuid或--user，请确保用户可以写入/var/log或现有的/var/log/some.log。不过，最好的方法是让该用户拥有一个/var/log/subdir/。|offset|length|style|CODE|505645|entityMap^0|0|0|8|7|G|6|W|8|18|H|27|G|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$]]

You need to do:

<pre><code>start-stop-daemon --start --quiet --chuid $DAEMONUSER \
 --make-pidfile --pidfile $PIDFILE --background \
 --exec /bin/bash -- -c "$DAEMON $DAEMON_ARGS &gt; /var/log/some.log 2&gt;&amp;1"
</code></pre>

Also if you use <code>--chuid</code> or <code>--user</code>, make sure the user can write to <code>/var/log</code> or the existing <code>/var/log/some.log</code>. The best way is to have that user own a <code>/var/log/subdir/</code> though.

blocks|key|721846|text|这样如何：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|721847|sudo+-u+myuser+-i+start-stop-daemon+...|code-block|syntax|javascript|721848|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

How about:

<pre><code>sudo -u myuser -i start-stop-daemon ...
</code></pre>

blocks|key|721891|text|我不确定"$DAEMON+$DAEMON_ARGS+>/var/2>&1/ome.log+2>&1“是否会关闭日志文件的文件描述符...这意味着如果您的守护进程永远运行，我不确定logrotate或其他清理磁盘空间的机制是否有效。因为它是>而不是>>，所以建议的命令还会在重启时截断现有日志。如果您想了解守护进程崩溃并自动重新启动的原因，这可能没有太大帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|721892|另一个选项可能是"$DAEMON+%7C+logger“。logger是一个将记录到syslog+(/var/+log+/messages)的命令。如果你也需要stderr，我想你可以使用"$DAEMON+1>&2+%7C+logger“|721893|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'm not sure if "$DAEMON $DAEMON_ARGS > /var/log/some.log 2>&amp;1" will ever close the file descriptor for the log file... which means if your daemon runs forever, I'm not sure that logrotate or other mechanisms for cleaning up disk space would work. Since it's > instead of >>, the suggested command would also truncate existing logs on restart. If you want to see why the daemon crashed, and it restarts automatically, that might not be very helpful.

Another option might be "$DAEMON | logger". logger is a command that will log to syslog (/var/log/messages). If you need stderr too, I think you could use "$DAEMON 1>&amp;2 | logger"

blocks|key|721972|text|对ypocat的回答进行扩展，因为它不让我发表评论：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|721973|start-stop-daemon+--start+--quiet+--chuid+$DAEMONUSER++++\
+--make-pidfile+--pidfile+$PIDFILE+--background+++++++\
+--startas+/bin/bash+--+-c+"exec+$DAEMON+$DAEMON_ARGS+>+/var/log/some.log+2>&1"|code-block|syntax|javascript|721974|使用exec运行守护进程允许stop正确地停止子进程，而不仅仅是bash父进程。|offset|length|style|CODE|721975|使用--startas而不是--exec可以确保进程能够被其pid正确检测到，并且如果多次调用start，也不会错误地启动守护进程的多个实例。否则，start-stop-daemon将查找/bin/bash进程并忽略运行该守护进程的实际子进程。|721976|entityMap^0|0|0|2|4|0|2|9|E|6|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@$I|W|J|X|K|L]|$I|Y|J|Z|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

To expand on ypocat's answer, since it won't let me comment:

<pre><code>start-stop-daemon --start --quiet --chuid $DAEMONUSER \
 --make-pidfile --pidfile $PIDFILE --background \
 --startas /bin/bash -- -c "exec $DAEMON $DAEMON_ARGS &gt; /var/log/some.log 2&gt;&amp;1"
</code></pre>

Using <code>exec</code> to run the daemon allows stop to correctly stop the child process instead of just the bash parent.

Using <code>--startas</code> instead of <code>--exec</code> ensures that the process will be correctly detected by its pid and won't erroneously start multiple instances of the daemon if start is called multiple times. Otherwise, start-stop-daemon will look for a /bin/bash process and ignore the actual child process running the daemon.

blocks|key|505948|text|start-stop-daemon有一个选项--no-close，意思是“在运行后台时不要关闭任何fd”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|505949|start-stop-daemon+--start+--quiet+--chuid+$DAEMONUSER++++\
++++--make-pidfile+--pidfile+$PIDFILE+--background+++++++\
++++--exec+$DAEMON+--no-close+\
++++--+$DAEMON_ARGS+>+/var/log/some.log+2>&1|code-block|syntax|javascript|505950|这会将进程start-stop-daemon的stdout/stderr重定向到该文件。并且您的可执行文件从其父进程start-stop-daemon继承stdout/stderr。|505951|entityMap^0|0|H|M|A|0|0|5|H|1M|H|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

there is an option <code>--no-close</code> for <code>start-stop-daemon</code>, which means &quot;don't close any fd when it's run background.&quot;
<pre class="lang-sh prettyprint-override"><code>start-stop-daemon --start --quiet --chuid $DAEMONUSER \
 --make-pidfile --pidfile $PIDFILE --background \
 --exec $DAEMON --no-close \
 -- $DAEMON_ARGS &gt; /var/log/some.log 2&gt;&amp;1
</code></pre>
this redirect the stdout/stderr of process <code>start-stop-daemon</code> to the file. and your executable inherits stdout/stderr from its parent process <code>start-stop-daemon</code>.

I am using an init script to run a simple process, which is started with:

<pre><code>start-stop-daemon --start --quiet --chuid $DAEMONUSER \
 --make-pidfile --pidfile $PIDFILE --background \
 --exec $DAEMON $DAEMON_ARGS
</code></pre>

The process called $DAEMON usually prints log information to its standard output. As far as I can tell this data is not being stored anywhere.

I would like to write or append the stdout of $DAEMON to a file somewhere.

The only solution I know is to tell start-stop-daemon to call a shellscript instead of $DAEMON directly; the script then calls $DAEMON and writes to the logfile. But that requires an extra script which, like modifying the daemon itself, seems the wrong way to solve such a common task.

How can I log the stdout of a process started by start-stop-daemon?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我使用一个init脚本来运行一个简单的进程，该进程从以下命令开始：start-stop-daemon --start --quiet --chuid $DAEMONUSER    \    --make-pidfile --pidfile $PIDFILE --background       \    --exec ...

问如何记录start-stop-daemon启动的进程的stdout？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何记录start-stop-daemon启动的进程的stdout？EN