2008-04-12 Micah Cowan <micah@cowan.name>
+ * mswindows.c (fake_fork_child): Don't mention that we're
+ backgrounding if --quiet is used.
+
+ * utils.c (fork_to_background): Likewise.
+
+2008-04-12 Rabin Vincent <rabin@rab.in>
+
* mswindows.c (fake_fork_child): Don't create a logfile for
--background when --quiet is used, but not --server-response.
- Don't mention that we're backgrounding if --quiet is used. Based
- on a patch submitted by Rabin Vincent <rabin@rab.in>. Fixes bug
- #20917.
+ Fixes bug #20917.
* utils.c (fork_to_background): Likewise.
event = info->event;
info->logfile_changed = false;
- if (opt.quiet && !opt.server_response)
- {
- log_close ();
- }
- if (!opt.lfilename)
+ if (!opt.lfilename && (!opt.quiet || opt.server_response))
{
/* See utils:fork_to_background for explanation. */
FILE *new_log_fp = unique_create (DEFAULT_LOGFILE, false, &opt.lfilename);
/* Whether we arrange our own version of opt.lfilename here. */
bool logfile_changed = false;
- if (opt.quiet && !opt.server_response)
- {
- /* Don't bother with a logfile, there are virtually no logs we
- issue in quiet mode. (Server responses in FTP are the
- exception, when enabled.) */
- log_close ();
- }
- if (!opt.lfilename)
+ if (!opt.lfilename && (!opt.quiet || opt.server_response))
{
/* We must create the file immediately to avoid either a race
condition (which arises from using unique_name and failing to