-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.223 2009/08/04 16:08:35 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.224 2009/08/24 20:08:31 tgl Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
</para>
</listitem>
</varlistentry>
-
+
+ <varlistentry id="guc-silent-mode" xreflabel="silent_mode">
+ <term><varname>silent_mode</varname> (<type>boolean</type>)</term>
+ <indexterm>
+ <primary><varname>silent_mode</> configuration parameter</primary>
+ </indexterm>
+ <listitem>
+ <para>
+ Runs the server silently. If this parameter is set, the server
+ will automatically run in background and disassociate from the
+ controlling terminal.
+ This parameter can only be set at server start.
+ </para>
+
+ <caution>
+ <para>
+ When this parameter is set,
+ the server's standard output and standard error are redirected
+ to the file <filename>postmaster.log</> within the data directory.
+ There is no provision for rotating this file, so it will grow
+ indefinitely unless server log output is redirected elsewhere
+ by other settings. It is recommended that <varname>log_destination</>
+ be set to <literal>syslog</> or that <varname>logging_collector</> be
+ enabled when using this option. Even with those measures, errors
+ reported early during startup may appear in
+ <filename>postmaster.log</> rather than the normal log destination.
+ </para>
+ </caution>
+ </listitem>
+ </varlistentry>
+
</variablelist>
</sect2>
<sect2 id="runtime-config-logging-when">
</listitem>
</varlistentry>
- <varlistentry id="guc-silent-mode" xreflabel="silent_mode">
- <term><varname>silent_mode</varname> (<type>boolean</type>)</term>
- <indexterm>
- <primary><varname>silent_mode</> configuration parameter</primary>
- </indexterm>
- <listitem>
- <para>
- Runs the server silently. If this parameter is set, the server
- will automatically run in background and any controlling
- terminals are disassociated.
- The server's standard output and standard error are redirected
- to <literal>/dev/null</>, so any messages sent to them will be lost.
- Unless <application>syslog</> logging is selected or
- <varname>logging_collector</> is enabled, using this parameter
- is discouraged because it makes it impossible to see error messages.
- This parameter can only be set at server start.
- </para>
- </listitem>
- </varlistentry>
-
</variablelist>
<para>
*
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/postmaster/postmaster.c,v 1.589 2009/08/24 18:09:37 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/postmaster/postmaster.c,v 1.590 2009/08/24 20:08:32 tgl Exp $
*
* NOTES
*
/* still more option variables */
bool EnableSSL = false;
-bool SilentMode = false; /* silent mode (-S) */
+bool SilentMode = false; /* silent_mode */
int PreAuthDelay = 0;
int AuthenticationTimeout = 60;
}
/*
- * Fork away from controlling terminal, if -S specified.
+ * Fork away from controlling terminal, if silent_mode specified.
*
* Must do this before we grab any interlock files, else the interlocks
* will show the wrong PID.
*/
set_max_safe_fds();
- /*
- * Load configuration files for client authentication.
- */
- if (!load_hba())
- {
- /*
- * It makes no sense continue if we fail to load the HBA file, since
- * there is no way to connect to the database in this case.
- */
- ereport(FATAL,
- (errmsg("could not load pg_hba.conf")));
- }
- load_ident();
-
/*
* Initialize the list of active backends.
*/
*/
autovac_init();
+ /*
+ * Load configuration files for client authentication.
+ */
+ if (!load_hba())
+ {
+ /*
+ * It makes no sense to continue if we fail to load the HBA file,
+ * since there is no way to connect to the database in this case.
+ */
+ ereport(FATAL,
+ (errmsg("could not load pg_hba.conf")));
+ }
+ load_ident();
+
/*
* Remember postmaster startup time
*/
/*
- * Fork away from the controlling terminal (-S option)
+ * Fork away from the controlling terminal (silent_mode option)
+ *
+ * Since this requires disconnecting from stdin/stdout/stderr (in case they're
+ * linked to the terminal), we re-point stdin to /dev/null and stdout/stderr
+ * to "postmaster.log" in the data directory, where we're already chdir'd.
*/
static void
pmdaemonize(void)
{
#ifndef WIN32
- int i;
+ const char *pmlogname = "postmaster.log";
+ int dvnull;
+ int pmlog;
pid_t pid;
+ int res;
+
+ /*
+ * Make sure we can open the files we're going to redirect to. If this
+ * fails, we want to complain before disconnecting. Mention the full path
+ * of the logfile in the error message, even though we address it by
+ * relative path.
+ */
+ dvnull = open(DEVNULL, O_RDONLY, 0);
+ if (dvnull < 0)
+ {
+ write_stderr("%s: could not open file \"%s\": %s\n",
+ progname, DEVNULL, strerror(errno));
+ ExitPostmaster(1);
+ }
+ pmlog = open(pmlogname, O_CREAT | O_WRONLY | O_APPEND, 0600);
+ if (pmlog < 0)
+ {
+ write_stderr("%s: could not open log file \"%s/%s\": %s\n",
+ progname, DataDir, pmlogname, strerror(errno));
+ ExitPostmaster(1);
+ }
+ /*
+ * Okay to fork.
+ */
pid = fork_process();
if (pid == (pid_t) -1)
{
MyStartTime = time(NULL);
/*
- * GH: If there's no setsid(), we hopefully don't need silent mode. Until
- * there's a better solution.
+ * Some systems use setsid() to dissociate from the TTY's process group,
+ * while on others it depends on stdin/stdout/stderr. Do both if possible.
*/
#ifdef HAVE_SETSID
if (setsid() < 0)
ExitPostmaster(1);
}
#endif
- i = open(DEVNULL, O_RDWR, 0);
- dup2(i, 0);
- dup2(i, 1);
- dup2(i, 2);
- close(i);
+
+ /*
+ * Reassociate stdin/stdout/stderr. fork_process() cleared any pending
+ * output, so this should be safe. The only plausible error is EINTR,
+ * which just means we should retry.
+ */
+ do {
+ res = dup2(dvnull, 0);
+ } while (res < 0 && errno == EINTR);
+ close(dvnull);
+ do {
+ res = dup2(pmlog, 1);
+ } while (res < 0 && errno == EINTR);
+ do {
+ res = dup2(pmlog, 2);
+ } while (res < 0 && errno == EINTR);
+ close(pmlog);
#else /* WIN32 */
/* not supported */
- elog(FATAL, "SilentMode not supported under WIN32");
+ elog(FATAL, "silent_mode is not supported under Windows");
#endif /* WIN32 */
}
if (!load_hba())
{
/*
- * It makes no sense continue if we fail to load the HBA file, since
- * there is no way to connect to the database in this case.
+ * It makes no sense to continue if we fail to load the HBA file,
+ * since there is no way to connect to the database in this case.
*/
ereport(FATAL,
(errmsg("could not load pg_hba.conf")));
* Written by Peter Eisentraut <peter_e@gmx.net>.
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/utils/misc/guc.c,v 1.510 2009/08/04 16:08:36 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/misc/guc.c,v 1.511 2009/08/24 20:08:32 tgl Exp $
*
*--------------------------------------------------------------------
*/
true, NULL, NULL
},
{
- {"silent_mode", PGC_POSTMASTER, LOGGING_WHEN,
+ {"silent_mode", PGC_POSTMASTER, LOGGING_WHERE,
gettext_noop("Runs the server silently."),
gettext_noop("If this parameter is set, the server will automatically run in the "
"background and any controlling terminals are dissociated.")
projects / postgresql / commitdiff