* Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
@ 2004-05-24 15:14 gert_de_boer
2004-05-26 20:34 ` Brian Ford
0 siblings, 1 reply; 8+ messages in thread
From: gert_de_boer @ 2004-05-24 15:14 UTC (permalink / raw)
To: cygwin
The trick worked for CRON. I let the cron service run under the local
administration account with the additional rights as explained in the
openssh.README.
But mutt still does not work. I do not get any clear message in the event
viewer.
Regards,
Gert de Boer
PS How do I get my mails under the tread in the maillist that I am
answering to?
> It all works without any problem on Windows XP and Windows 2000.
>
> So it seems something has changed in Windows 2003: for some reason mutt
> cannot trigger ssmtp to do its job.
>
> Something similar seems to happen between the CYGWIN cron service and the
> scripts it is supposed to start. Nothing happens, but if I look in the
> eventviewer I see the following order of events:
Please read the Windows 2003 Server section of
/usr/share/doc/Cygwin/openssh.README and see if that helps. I know it
sounds weird, but trust me, it is relevant.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
2004-05-24 15:14 mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127' gert_de_boer
@ 2004-05-26 20:34 ` Brian Ford
0 siblings, 0 replies; 8+ messages in thread
From: Brian Ford @ 2004-05-26 20:34 UTC (permalink / raw)
To: gert_de_boer; +Cc: cygwin
On Mon, 24 May 2004, gert_de_boer wrote:
> The trick worked for CRON. I let the cron service run under the local
> administration account with the additional rights as explained in the
> openssh.README.
Glad I could help, at least a little.
> But mutt still does not work. I do not get any clear message in the event
> viewer.
Sorry. I don't use mutt or ssmtp, so I'm out of ideas.
> Regards,
>
> Gert de Boer
>
> PS How do I get my mails under the tread in the maillist that I am
> answering to?
Get your mailer to add the header:
In-Reply-To: <Message-ID>
Normally, this happens automatically when you reply to a message.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
2004-05-19 13:16 gert_de_boer
2004-05-19 14:28 ` Brian Ford
@ 2004-05-19 15:11 ` Mark Bohlman
1 sibling, 0 replies; 8+ messages in thread
From: Mark Bohlman @ 2004-05-19 15:11 UTC (permalink / raw)
To: cygwin
gert_de_boer@ch.schindler.com wrote:
>
>
>
> Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
> Windows 2003 server.
>
> As an example of what happens:
>
> $ echo hallo | mutt -s new_test myname@mycompany.com
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
>
> The error is exactly the same as when I have a wrong 'sendmail' defined in
> my .muttrc on a server where cygwin runs without any problem. However I
> defined it correct:
> set sendmail=/usr/sbin/ssmtp
>
> Executing ssmtp on its own delivers an empty mail at myname@mycompany.com,
> so the error is not there.
>
> It all works without any problem on Windows XP and Windows 2000.
>
> So it seems something has changed in Windows 2003: for some reason mutt
> cannot trigger ssmtp to do its job.
>
> Something similar seems to happen between the CYGWIN cron service and the
> scripts it is supposed to start. Nothing happens, but if I look in the
> eventviewer I see the following order of events:
>
> PID 3188: (myaccount) RELOAD (tabs/myaccount)
>
> PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
>
> PID 3392: (CRON) error (can't switchuser context)
>
> So it is just an idea of mine that somehow (some) programs are not able to
> start others, due to some rigid security settings.
>
> BTW, all the above is done as with a group account with administrator
> rights on the server.
>
> Gert de Boer
>
> gert de boer at ch schindler com
>
> cygcheck.out:
> (See attached file: cygcheck.out):
>
I had a similar problem on Win2K until I checked the
/etc/ssmtp/ssmtp.conf file and found an improper setting. Also check
the ~/.muttrc file for correct settings. Fixing this got rid of the
same error message on my system. See also /usr/share/doc/mutt-xxx.README.
Hope this helps.
-- Mark
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
@ 2004-05-19 15:10 Buchbinder, Barry (NIH/NIAID)
0 siblings, 0 replies; 8+ messages in thread
From: Buchbinder, Barry (NIH/NIAID) @ 2004-05-19 15:10 UTC (permalink / raw)
To: cygwin
Sorry for the noise.
-----Original Message-----
From: Luc Hermitte [mailto:hermitte@free.fr]
Sent: Wednesday, May 19, 2004 10:09 AM
To: cygwin@cygwin.com
Subject: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited
127'
* On Wed, May 19, 2004 at 09:16:11AM -0400, Buchbinder, Barry (NIH/NIAID)
<BBuchbinder@niaid.nih.gov> wrote:
> If I remember correctly (I have not played with mutt for quite a
> while), mutt can connect directly to a IMAP or POP server. So might
> you be able to eliminate the use of ssmtp and have mutt send mail
> directly to the place that ssmtp sends it?
IMAP and POP3 protocols are meant to import emails.
SMTP is meant to export (/send) them.
I do use mutt with ssmtp to send messages like this one and I read my
email directly on an IMAP server.
Unfortunatelly, I can't help much. I use XP and every thing is working
fine. ssmtp is used to send the emails to a local STMP server (Hamster),
which then relays my messages to the SMTP servers of my ISP.
The only times I get the error
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
is when Hamster is not running -- as ssmtp can't reach the SMTP server
it must send the messages to.
But I'm not sure it is of any help here.
--
Luc Hermitte
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
2004-05-19 13:16 gert_de_boer
@ 2004-05-19 14:28 ` Brian Ford
2004-05-19 15:11 ` Mark Bohlman
1 sibling, 0 replies; 8+ messages in thread
From: Brian Ford @ 2004-05-19 14:28 UTC (permalink / raw)
To: gert_de_boer; +Cc: cygwin
On Wed, 19 May 2004, gert_de_boer wrote:
> Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
> Windows 2003 server.
>
> As an example of what happens:
>
> $ echo hallo | mutt -s new_test myname@mycompany.com
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
>
> The error is exactly the same as when I have a wrong 'sendmail' defined in
> my .muttrc on a server where cygwin runs without any problem. However I
> defined it correct:
> set sendmail=/usr/sbin/ssmtp
>
> Executing ssmtp on its own delivers an empty mail at myname@mycompany.com,
> so the error is not there.
>
> It all works without any problem on Windows XP and Windows 2000.
>
> So it seems something has changed in Windows 2003: for some reason mutt
> cannot trigger ssmtp to do its job.
>
> Something similar seems to happen between the CYGWIN cron service and the
> scripts it is supposed to start. Nothing happens, but if I look in the
> eventviewer I see the following order of events:
>
> PID 3188: (myaccount) RELOAD (tabs/myaccount)
>
> PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
>
> PID 3392: (CRON) error (can't switchuser context)
>
> So it is just an idea of mine that somehow (some) programs are not able to
> start others, due to some rigid security settings.
>
> BTW, all the above is done as with a group account with administrator
> rights on the server.
Please read the Windows 2003 Server section of
/usr/share/doc/Cygwin/openssh.README and see if that helps. I know it
sounds weird, but trust me, it is relevant.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
2004-05-19 13:54 Buchbinder, Barry (NIH/NIAID)
@ 2004-05-19 14:07 ` Luc Hermitte
0 siblings, 0 replies; 8+ messages in thread
From: Luc Hermitte @ 2004-05-19 14:07 UTC (permalink / raw)
To: cygwin
* On Wed, May 19, 2004 at 09:16:11AM -0400, Buchbinder, Barry (NIH/NIAID) <BBuchbinder@niaid.nih.gov> wrote:
> If I remember correctly (I have not played with mutt for quite a
> while), mutt can connect directly to a IMAP or POP server. So might
> you be able to eliminate the use of ssmtp and have mutt send mail
> directly to the place that ssmtp sends it?
IMAP and POP3 protocols are meant to import emails.
SMTP is meant to export (/send) them.
I do use mutt with ssmtp to send messages like this one and I read my
email directly on an IMAP server.
Unfortunatelly, I can't help much. I use XP and every thing is working
fine. ssmtp is used to send the emails to a local STMP server (Hamster),
which then relays my messages to the SMTP servers of my ISP.
The only times I get the error
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
is when Hamster is not running -- as ssmtp can't reach the SMTP server
it must send the messages to.
But I'm not sure it is of any help here.
--
Luc Hermitte
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
@ 2004-05-19 13:54 Buchbinder, Barry (NIH/NIAID)
2004-05-19 14:07 ` Luc Hermitte
0 siblings, 1 reply; 8+ messages in thread
From: Buchbinder, Barry (NIH/NIAID) @ 2004-05-19 13:54 UTC (permalink / raw)
To: 'gert_de_boer@ch.schindler.com', cygwin
If I remember correctly (I have not played with mutt for quite a while),
mutt can connect directly to a IMAP or POP server. So might you be able to
eliminate the use of ssmtp and have mutt send mail directly to the place
that ssmtp sends it?
-----Original Message-----
From: gert_de_boer@ch.schindler.com [mailto:gert_de_boer@ch.schindler.com]
Sent: Wednesday, May 19, 2004 7:53 AM
To: cygwin@cygwin.com
Subject: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
Windows 2003 server.
As an example of what happens:
$ echo hallo | mutt -s new_test myname@mycompany.com
Error sending message, child exited 127 (Exec error.).
Could not send the message.
The error is exactly the same as when I have a wrong 'sendmail' defined in
my .muttrc on a server where cygwin runs without any problem. However I
defined it correct:
set sendmail=/usr/sbin/ssmtp
Executing ssmtp on its own delivers an empty mail at myname@mycompany.com,
so the error is not there.
It all works without any problem on Windows XP and Windows 2000.
So it seems something has changed in Windows 2003: for some reason mutt
cannot trigger ssmtp to do its job.
Something similar seems to happen between the CYGWIN cron service and the
scripts it is supposed to start. Nothing happens, but if I look in the
eventviewer I see the following order of events:
PID 3188: (myaccount) RELOAD (tabs/myaccount)
PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
PID 3392: (CRON) error (can't switchuser context)
So it is just an idea of mine that somehow (some) programs are not able to
start others, due to some rigid security settings.
BTW, all the above is done as with a group account with administrator
rights on the server.
Gert de Boer
gert de boer at ch schindler com
cygcheck.out:
(See attached file: cygcheck.out):
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
* mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
@ 2004-05-19 13:16 gert_de_boer
2004-05-19 14:28 ` Brian Ford
2004-05-19 15:11 ` Mark Bohlman
0 siblings, 2 replies; 8+ messages in thread
From: gert_de_boer @ 2004-05-19 13:16 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
Windows 2003 server.
As an example of what happens:
$ echo hallo | mutt -s new_test myname@mycompany.com
Error sending message, child exited 127 (Exec error.).
Could not send the message.
The error is exactly the same as when I have a wrong 'sendmail' defined in
my .muttrc on a server where cygwin runs without any problem. However I
defined it correct:
set sendmail=/usr/sbin/ssmtp
Executing ssmtp on its own delivers an empty mail at myname@mycompany.com,
so the error is not there.
It all works without any problem on Windows XP and Windows 2000.
So it seems something has changed in Windows 2003: for some reason mutt
cannot trigger ssmtp to do its job.
Something similar seems to happen between the CYGWIN cron service and the
scripts it is supposed to start. Nothing happens, but if I look in the
eventviewer I see the following order of events:
PID 3188: (myaccount) RELOAD (tabs/myaccount)
PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
PID 3392: (CRON) error (can't switchuser context)
So it is just an idea of mine that somehow (some) programs are not able to
start others, due to some rigid security settings.
BTW, all the above is done as with a group account with administrator
rights on the server.
Gert de Boer
gert de boer at ch schindler com
cygcheck.out:
(See attached file: cygcheck.out):
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 13239 bytes --]
$ cygcheck.exe -s -v -r
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Wed May 19 12:42:27 2004
Windows .NET Server Ver 5.2 Build 3790
Path: C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\cygwin\usr\X11R6\bin
C:\cygwin\bin
e:\oracle\ora81\bin
c:\Program Files\Oracle\jre\1.1.7\bin
c:\Perl\bin\
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
c:\Program Files\Support Tools\
c:\Program Files\IBM\Director\bin
c:\Program Files\mycompany\RMCC
c:\ORACLE\Admin\RMCC\805to8i
c:\Program Files\JavaSoft\JRE\1.3.1\bin
C:\cygwin\bin
Output from C:\cygwin\bin\id.exe (nontsec)
UID: 22940(myaccount) GID: 10513(Domain Users)
10513(Domain Users)
Output from C:\cygwin\bin\id.exe (ntsec)
UID: 22940(myaccount) GID: 10513(Domain Users)
0(root)
544(Administrators) 545(Users)
1006(ORA_DBA)
10513(Domain Users) 11990(GG_SCH_RegeditYes)
22810(GO_SCH_Auftragsunt-OP_R)
22817(GO_SCH_Bonus_SRE_C) 22638(GO_SCH_BonusDaten_R)
22641(GO_SCH_BonusEI_C)
22642(GO_SCH_BonusEI_R) 22647(GO_SCH_BonusFI_C)
22648(GO_SCH_BonusFI_R)
22717(GO_SCH_BonusHinweise_C) 22718(GO_SCH_BonusHinweise_R)
22649(GO_SCH_BonusHR_C)
22650(GO_SCH_BonusHR_R) 22640(GO_SCH_BonusMADaten_R)
22657(GO_SCH_BonusSCM_C)
22658(GO_SCH_BonusSCM_R) 22659(GO_SCH_BonusVGL_C)
22660(GO_SCH_BonusVGL_R)
22972(GO_SCH_IT-ENT-PWD_C)
SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS
CYGWIN = `"tty ntsec"'
HOME = `C:\cygwin\home\myaccount'
MAKE_MODE = `unix'
PWD = `/home/myaccount'
USER = `myaccount'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
CLUSTERLOG = `C:\WINDOWS\Cluster\cluster.log'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `servername'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
CVS_RSH = `/bin/ssh'
HOMEDRIVE = `C:'
HOMEPATH = `\cygwin\home\myaccount'
HOSTNAME = `servername'
INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:'
JAVA_HOME = `D:\j2sdk1.4.2_04'
LOGNAME = `myaccount'
LOGONSERVER = `\\logonserver'
MAIL = `/home/myaccount/Mail/inbox'
MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man'
NLS_LANG = `TRADITIONAL CHINESE_CHINA.UTF8'
NUMBER_OF_PROCESSORS = `1'
OLDPWD = `/home/myaccount'
ORACLE_BASE = `e:\oracle'
ORACLE_SID = `utf'
ORA_NLS32 = `e:\oracle\ora81\ocommon\nls\admin\data'
ORA_NLS33 = `e:\oracle\ora81\ocommon\nls\admin\data'
ORA_NLS = `e:\oracle\ora81\ocommon\nls\admin\data'
OS = `Windows_NT'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 5 Stepping 2, GenuineIntel'
PROCESSOR_LEVEL = `6'
PROCESSOR_REVISION = `0502'
PROGRAMFILES = `C:\Program Files'
PS1 = `\[\033]0;\w\007
\033[32m\]\u@\h \[\033[33m\w\033[0m\]
$ '
RFC_INI = `C:\WINDOWS\saprfc.ini'
SHELL = `/bin/bash'
SHLVL = `1'
SSH_CLIENT = `10.17.5.38 1428 22'
SSH_CONNECTION = `10.17.5.38 1428 10.17.5.18 22'
SSH_TTY = `/dev/tty0'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `c:\WINDOWS\TEMP'
TERM = `xterm'
TMP = `c:\WINDOWS\TEMP'
TOMCAT_HOME = `C:\tomcat-jakarta'
TZ = `WEST-1WEDT-2,M3.5.0/2,M10.5.0/3'
USERDOMAIN = `SCH'
USERNAME = `myaccount'
WINDIR = `C:\WINDOWS'
_ = `/usr/bin/cygcheck.exe'
POSIXLY_CORRECT = `1'
HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x00000022
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
(default) = `C:\cygwin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:\cygwin/bin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:\cygwin/lib'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
a: fd N/A N/A
c: hd NTFS 4094Mb 79% CP CS UN PA FC OS
d: hd NTFS 4581Mb 66% CP CS UN PA FC Data
e: hd NTFS 8675Mb 15% CP CS UN PA FC Data
z: cd N/A N/A
C:\cygwin / system binmode
C:\cygwin/bin /usr/bin system binmode
C:\cygwin/lib /usr/lib system binmode
. /cygdrive system binmode,cygdrive
Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Not Found: cpp (good!)
Found: C:\cygwin\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ls.exe
Not Found: make
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
61k 2003/08/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2003/8/9 7:35
7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2003/10/19 8:57
841k 2004/03/17 C:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-0.9.7.dll" v0.0 ts=2004/3/17 22:58
617k 2004/03/22 C:\cygwin\bin\cygcurl-2.dll - os=4.0 img=1.0 sys=4.0
"cygcurl-2.dll" v0.0 ts=2004/3/22 15:52
22k 2004/02/10 C:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0
"cygcygipc-2.dll" v0.0 ts=2004/2/10 2:48
45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
"cygform5.dll" v0.0 ts=2001/4/25 6:28
35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0
"cygform6.dll" v0.0 ts=2002/1/9 6:03
48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
"cygform7.dll" v0.0 ts=2003/8/9 10:25
69k 2003/08/10 C:\cygwin\bin\cyggettextlib-0-12-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextlib-0-12-1.dll" v0.0 ts=2003/8/10 23:10
12k 2003/08/10 C:\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0
"cyggettextpo-0.dll" v0.0 ts=2003/8/10 23:11
134k 2003/08/10 C:\cygwin\bin\cyggettextsrc-0-12-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextsrc-0-12-1.dll" v0.0 ts=2003/8/10 23:10
17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
"cyghistory4.dll" v0.0 ts=2001/1/7 4:34
29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
"cyghistory5.dll" v0.0 ts=2003/8/11 0:16
958k 2003/08/10 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2003/8/10 21:57
22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
"cygintl-1.dll" v0.0 ts=2001/12/13 9:28
37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
"cygintl-2.dll" v0.0 ts=2003/8/10 22:50
26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
"cygmenu5.dll" v0.0 ts=2001/4/25 6:27
20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0
"cygmenu6.dll" v0.0 ts=2002/1/9 6:03
29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
"cygmenu7.dll" v0.0 ts=2003/8/9 10:25
15k 2003/11/20 C:\cygwin\bin\cygminires.dll - os=4.0 img=0.97 sys=4.0
"cygminires.dll" v0.0 ts=2003/11/20 1:55
156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++5.dll" v0.0 ts=2001/4/25 6:29
175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++6.dll" v0.0 ts=2002/1/9 6:03
226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses5.dll" v0.0 ts=2001/4/25 6:17
202k 2002/01/09 C:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses6.dll" v0.0 ts=2002/1/9 6:03
224k 2003/08/09 C:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
"cygncurses7.dll" v0.0 ts=2003/8/9 10:24
15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
"cygpanel5.dll" v0.0 ts=2001/4/25 6:27
12k 2002/01/09 C:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0
"cygpanel6.dll" v0.0 ts=2002/1/9 6:03
19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
"cygpanel7.dll" v0.0 ts=2003/8/9 10:24
62k 2003/12/11 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-0.dll" v0.0 ts=2003/12/11 17:01
63k 2003/04/11 C:\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0
"cygpcre.dll" v0.0 ts=2003/4/11 9:31
9k 2003/12/11 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix-0.dll" v0.0 ts=2003/12/11 17:01
61k 2003/04/11 C:\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix.dll" v0.0 ts=2003/4/11 9:31
22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2002/6/9 6:45
108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
"cygreadline4.dll" v0.0 ts=2001/1/7 4:34
148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
"cygreadline5.dll" v0.0 ts=2003/8/11 0:16
66k 2001/11/20 C:\cygwin\bin\cygregex.dll - os=4.0 img=1.0 sys=4.0
"cygregex.dll" v0.0 ts=2001/11/20 14:44
171k 2004/03/17 C:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygssl-0.9.7.dll" v0.0 ts=2004/3/17 22:58
61k 2003/12/04 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2003/12/4 3:03
1100k 2004/03/19 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2004/3/19 4:05
Cygwin DLL version info:
DLL version: 1.5.9
DLL epoch: 19
DLL bad signal mask: 19005
DLL old termios: 5
DLL malloc env: 28
API major: 0
API minor: 112
Shared data: 4
DLL identifier: cygwin1
Mount registry: 2
Cygnus registry name: Cygnus Solutions
Cygwin registry name: Cygwin
Program options name: Program Options
Cygwin mount registry name: mounts v2
Cygdrive flags: cygdrive flags
Cygdrive prefix: cygdrive prefix
Cygdrive default prefix:
Build date: Thu Mar 18 23:05:18 EST 2004
Shared id: cygwin1S4
Cygwin Package Information
Last downloaded files to: Z:\
Last downloaded files from: Z:\
Package Version
_update-info-dir 00227-1
ash 20040127-1
base-files 2.6-1
base-passwd 1.1-1
bash 2.05b-16
binutils 20040312-1
bzip2 1.0.2-5
clear 1.0-1
cpio 2.5-3
cron 3.0.1-11
crypt 1.1-1
curl 7.11.1-1
cygipc 2.03-2
cygrunsrv 1.0-1
cygutils 1.2.5-1
cygwin 1.5.9-1
d 1.2.0-1
diffutils 2.8.7-1
ed 0.2-1
editrights 1.01-1
file 4.06-1
fileutils 4.1-2
findutils 4.1.7-4
fortune 1.8-2
gawk 3.1.3-4
grep 2.5-1
groff 1.18.1-2
gzip 1.3.5-1
inetutils 1.3.2-28
initscripts 0.9-1
less 381-1
libbz2_1 1.0.2-5
libgettextpo0 0.12.1-3
libiconv2 1.9.1-3
libintl1 0.10.40-1
libintl2 0.12.1-3
libncurses5 5.2-1
libncurses6 5.2-8
libncurses7 5.3-4
libpcre 4.1-1
libpcre0 4.5-1
libpopt0 1.6.4-4
libreadline4 4.1-2
libreadline5 4.3-5
login 1.9-7
lynx 2.8.4-7
man 1.5k-3
minires 0.97-1
mktemp 1.5-3
more 2.11o-1
mutt 1.4.1-2
nano 1.2.2-1
ncftp 3.1.4-1
ncurses 5.3-4
netcat 1.10-2
openssh 3.8.1p1-1
openssl 0.9.7d-1
proftpd 1.2.9-1
readline 4.3-5
regex 4.4-3
sed 4.0.9-2
setsid 0.0-3
sh-utils 2.0.15-4
ssmtp 2.60.4-3
sysvinit 2.84-4
tar 1.13.25-5
tcltk 20030901-1
termcap 20021106-2
terminfo 5.3_20030726-1
texinfo 4.2-4
textutils 2.0.21-1
time 1.7-1
unzip 5.50-5
vim 6.2.098-1
w32api 2.5-1
wget 1.9.1-1
which 1.5-2
zip 2.3-6
zlib 1.2.1-1
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2004-05-26 17:19 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-05-24 15:14 mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127' gert_de_boer
2004-05-26 20:34 ` Brian Ford
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 15:10 Buchbinder, Barry (NIH/NIAID)
2004-05-19 13:54 Buchbinder, Barry (NIH/NIAID)
2004-05-19 14:07 ` Luc Hermitte
2004-05-19 13:16 gert_de_boer
2004-05-19 14:28 ` Brian Ford
2004-05-19 15:11 ` Mark Bohlman
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).