I'm using exim and sshd which is working wonderfully on my w2k box.
My cygwin programs are recent as of the last 7 days if that matters.
What I can't figure out is how to get time/date stamps on the log
files such as sshd.log and exim_main.log. I got entries but when
they were made, who know
Replying to my own email for archives.
I didn't have syslogd running. Install script /bin/syslogd-config
I initially installed sshd with:
cygrunsrv -I sshd -d "CYGWIN sshd" -p /usr/sbin/sshd -a '-D -e'
changed to cygrunsrv -I sshd -d "CYGWIN sshd" -p /usr/sbin/sshd -a '-D'
Now I'm happier.
We
rograms are recent as of the last 7 days if that matters.
> >
> > What I can't figure out is how to get time/date stamps on the log
> > files such as sshd.log and exim_main.log. I got entries but when
> > they were made, who knows.
For the records, if syslogd is
8 08:58:12 /usr/bin/tail
I690811684268 76800 83948 08:58:12 /usr/bin/fold
2844 0 0 2844?0 08:58:12 D:\cygwin\bin\ps.exe
I'm mainly interested in the lines after Oct 17th. There are four lines with
timestamps 14:*:*. And then following the
I usually check the timestamps of the directories (and
cygwin-announce etc.) to see if something was released.
With lynx:
Aug 12 01:54 DirectoryXFree86
Aug 12 01:54 Directorydb
Aug 11 22:54 Directorylynx
Aug 11 22:54 Directoryssmtp
Aug 11 22:54 Directory
I downloaded two copies of setup-x86_64.exe, one a year or more
ago (v2.882) and one today (v2.895). Both of them have timestamps in my
filesystem of 11/27/2017, which I expect is being copied from the server I
downloaded from.
It would be helpful if these timestamps reflected when those
On Tue, Oct 19, 2004 at 04:17:33PM +, Christopher Cobb wrote:
>Can anyone shed any light on this?
The processes are not sorted in any way. They are displayed in the
same order as Windows presents them to cygwin.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
quot;ps -W".
As process indicates explicitly, the first four lines are from Oct 18th, the
next four from Oct 19th.
>From the ps -W output, you cannot discern this fact. From all appearances, the
first four lines with timestamps 14:*:* were from today (i.e., Oct 19th) in the
afternoon.
ur hours out. You probably need to set your timezone or
something.
> ps normally only shows timestamps for processes that began
> /today/. For
> processes that began before today, only the /date/ is shown
http://www.opengroup.org/onlinepubs/009695399/utilities/ps.html
demands no su
On Mon, 11 Aug 2003, Frédéric L. W. Meunier wrote:
> I usually check the timestamps of the directories (and
> cygwin-announce etc.) to see if something was released.
>
> With lynx:
>
> Aug 12 01:54 DirectoryXFree86
> Aug 12 01:54 Directorydb
> Aug 11 22:5
Jim Fehrle wrote:
I downloaded two copies of setup-x86_64.exe, one a year or more
ago (v2.882) and one today (v2.895). Both of them have timestamps in my
filesystem of 11/27/2017, which I expect is being copied from the server I
downloaded from.
It would be helpful if these timestamps
Date: Mon, 18 Mar 2019 01:55:36 -0700
Subject: Re: Misleading timestamps on setup-x86_64.exe
Mark Geisert wrote:
> Here are mine:
> /c/staging ls -l Cygwin??/setup*.exe
> -rwxrwxr-x+ 1 Mark None 1171475 Dec 20 01:18 Cygwin32/setup-x86.exe*
> -rwxrwxr-x+ 1 Mark None 1224211 Dec 20 01
Jim Fehrle wrote:
Date: Mon, 18 Mar 2019 01:55:36 -0700
Subject: Re: Misleading timestamps on setup-x86_64.exe
Mark Geisert wrote:
Here are mine:
/c/staging ls -l Cygwin??/setup*.exe
-rwxrwxr-x+ 1 Mark None 1171475 Dec 20 01:18 Cygwin32/setup-x86.exe*
-rwxrwxr-x+ 1 Mark None 1224211 Dec 20 01
On 2019-03-18 22:38, Mark Geisert wrote:
> On Mon, 18 Mar 2019 01:55:36 -0700, Jim Fehrle wrote:
>> Mark Geisert wrote:
>>> Here are mine:
>>> /c/staging ls -l Cygwin??/setup*.exe
>>> -rwxrwxr-x+ 1 Mark None 1171475 Dec 20 01:18 Cygwin32/setup-x86.exe*
>>> -rwxrwxr-x+ 1 Mark None 1224211 Dec 20 01:
Jim Fehrle writes:
> The file length matches exactly.
Then check the signature as well if you're still unsure.
> I downloaded by clicking the link at https://cygwin.com/. No idea about a
> proxy server. Is that something an ISP might set up? I'm working from my
> home, not an office. Not work
Date: Tue, 19 Mar 2019 19:34:38 +0100
Subject: Re: Misleading timestamps on setup-x86_64.exe
Achim Gratz writes:
> You didn't tell us how exactly you downloaded the file. If you
> donwloaded it onto an already existing file (overwriting it), it may
> have kept the old timestamp dep
Hi everybody,
I just noticed (due to high backup volume) that it seems like some Win7
Patch from mid-January 2012 timestamps are not transferred correctly any
more when using rsync.
So if I have a file on my host like this:
mc@Skynet03 /cygdrive/C/Windows/Installer
$ stat e6a7995.msi
File
Hello,
There seem to have been many changed md5sum's recently (timestamps above) under
_obsolete/ but also under GNOME/, automake/, jpeg/, pkgconfig/.
The replacement *.bz2 files are identical (of size 46 with md5sum
c616cffee0f344c37fd4e045a7a87054).
All ok?
Fergus
--
Unsubscribe
Fergus Daly wrote:
> There seem to have been many changed md5sum's recently (timestamps above)
> under _obsolete/ but also under GNOME/, automake/, jpeg/, pkgconfig/.
> The replacement *.bz2 files are identical (of size 46 with md5sum
> c616cffee0f344c37fd4e045a7a87054).
>
Hi
Can anybody help me with the following problem:
updating timestamps of files on a remote computer fails using tar, touch,
cp, mv
The commands "tar", "touch" , "cp -p", "mv" report errors when timestamps
have to be updated on a remote computer in a local
20 matches
Mail list logo
