public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygcheck's understanding of TZ
Date: Thu, 09 Jun 2011 21:06:00 -0000	[thread overview]
Message-ID: <20110609210632.GA1457@ednor.casa.cgf.cx> (raw)
In-Reply-To: <811AA35F-E300-46E5-9FE3-EE7D5E58194B@free.fr>

On Thu, Jun 09, 2011 at 09:50:02PM +0200, Denis Excoffier wrote:
>
>On 2011-06-09 21:26, Edward McGuire wrote:
>
>> cygcheck.cc:
>> [snip]
>> #include <sys/time.h>
>> [snip]
>>  time_t now;
>> [snip]
>>  printf ("\nCygwin Configuration Diagnostics\n");
>>  time (&now);
>>  printf ("Current System Time: %s\n", ctime (&now));
>>
>> It's using C RTL calls. And cygcheck(1) is linked with msvcrt.dll,
>> not GNU, and therefore cygcheck(1) has Microsoft C RTL behavior.
>> Microsoft C RTL does not support the pathname syntax extension;
>> that's a GNU thing.
>
>Exactly. That's why i suggested to use the UTC time zone (rather than
>an implicit local one), which msvcrt.dll probably is able to provide
>with no bug.
>
>We also could go a little bit beyond cgf's suggestion in
>http://cygwin.com/ml/cygwin/2011-06/msg00091.html
>(to use `date(1)') and remove completely the `Current System Time:'
>line in `cygcheck -s'.  Already, this time indication is not given
>under the other cygcheck's options.

We're not changing anything.  Having the date there is useful.

Again: you shouldn't use "cygcheck -s" as a method to find the system
date.

Just think of all of the other things that "cygcheck -s" is doing in
addition to displaying the date.  cygcheck is most definitely not
intended for this purpose.

cgf


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-06-09 21:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  7:47 EXCOFFIER Denis
2011-06-09  7:54 ` Thomas Wolff
2011-06-09 17:44   ` Buchbinder, Barry (NIH/NIAID) [E]
2011-06-09 17:39 ` Edward McGuire
2011-06-09 18:08   ` Charles Wilson
2011-06-09 19:27     ` Edward McGuire
2011-06-09 19:50       ` Denis Excoffier
2011-06-09 21:06         ` Christopher Faylor [this message]
2011-06-09 22:01           ` Edward McGuire
2011-06-10  7:25           ` Denis Excoffier
2011-06-10 14:07             ` Edward McGuire
2011-06-10 14:30             ` Christopher Faylor
2011-06-10 17:44               ` Denis Excoffier
2011-06-13 15:07                 ` Edward McGuire
2011-06-13 15:34                   ` Christopher Faylor
2011-06-14 15:05                     ` Lee Maschmeyer
2011-06-14 15:28                       ` Christopher Faylor
2011-06-14 17:30                         ` Lee Maschmeyer
2011-06-14 17:51                           ` Edward McGuire
2011-06-14 18:35                             ` Lee Maschmeyer
2011-06-14 19:19                               ` Edward McGuire
2011-06-14 19:22                                 ` Christopher Faylor
2011-06-14 19:21                           ` Christopher Faylor
2011-06-09 18:58   ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110609210632.GA1457@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).