Hi,
I've just updated the version of shutdown to v2.0-2 and it can be found at
a server near you.
This release fixes a build issue in the package. The 64-bit package actually
contained a 32-bit shutdown.exe
https://cygwin.com/ml/cygwin/2017-01/msg00194.html
FULL CHANGELOG (since shutdown-1
2017-01-16 18:52 GMT+01:00 Achim Gratz:
> There is a build or packaging error somewhere with the 64bit version:
> the shutdown.exe delivered with the x86_64 package is in fact a 32bit
> executable that refuses to work in 64bit Cygwin. Can you please correct
> and re-release the package?
Thanks fo
Frank Fesevur writes:
> I've just updated the version of shutdown to v2.0-1 and it can be
> found at a server near you.
There is a build or packaging error somewhere with the 64bit version:
the shutdown.exe delivered with the x86_64 package is in fact a 32bit
executable that refuses
Hi,
I've just updated the version of shutdown to v2.0-1 and it can be
found at a server near you.
FULL CHANGELOG (since shutdown-1.10-1)
==
* Added --install to install Windows Updates during shutdown/reboot.
The InitiateShutdown() Windows API ca
On Jun 17 10:34, Frank Fesevur wrote:
> Hi,
>
> I recently transferred my shutdown repo from my personal github
> acoount to the cygwin organization.
>
> Could anybody with the right permissions rename the repo to just "shutdown"?
Done.
Corinna
--
Corinna Vins
Hi,
I recently transferred my shutdown repo from my personal github
acoount to the cygwin organization.
Could anybody with the right permissions rename the repo to just "shutdown"?
Regards,
Frank
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://
Windows system shutdown
messages?
This seems entirely possible using the Win32 API.
For emacs-w32, it's probably straightforward to handle WM_ENDSESSION in
the message loop similarly to WM_CLOSE
This was indeed straightforward, so I went ahead and did it. But I
didn't try to do an
Windows system shutdown
messages?
This seems entirely possible using the Win32 API.
For emacs-w32, it's probably straightforward to handle WM_ENDSESSION in
the message loop similarly to WM_CLOSE
(Note that the process will be terminated if you return from processing
a WM_ENDSESSION message)
On 09/05/2016 14:35, Ken Brown wrote:
A Cygwin emacs user has asked
(http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23483) whether emacs can
auto-save files when he shuts down Windows from the Start Menu. Is
there a way for a Cygwin process to listen for Windows system shutdown
messages?
This
A Cygwin emacs user has asked
(http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23483) whether emacs can
auto-save files when he shuts down Windows from the Start Menu. Is
there a way for a Cygwin process to listen for Windows system shutdown
messages?
Ken
--
Problem reports: http
fact,
I think I'm down to just one now.
When I ctrl-D all Cygwin windows and exit X from taskbar
Then attempt to shutdown I get a MS window
popping up which asks if an xterm can be killed
In order to shutdown/reboot.
If I cancel and run windows task manager I see that
A dbus-daemon proces
A new version of the Cygwin shutdown 1.10-1 has been released and can
be found at a server near you.
BACKWARD COMPATIBILITY NOTE
===
Cygwin shutdown gives a POSIX/Linux-like shutdown experience and tries
to mimic the common Linux shutdown command line options as much as
On Jun 6 14:21, Frank Fesevur wrote:
> 2013/5/22 Corinna Vinschen:
> > After that, checking out the project is done using
> >
> > $ cvs -d :ext:@sourceware.org:/cvs/cygwin-apps co shutdown
>
> The code is in CVS.
>
> Since this is my first package and it uses
2013/5/22 Corinna Vinschen:
> After that, checking out the project is done using
>
> $ cvs -d :ext:@sourceware.org:/cvs/cygwin-apps co shutdown
The code is in CVS.
Since this is my first package and it uses the CVS I have a question
about the next steps.
If I understand things
se "cygwin-apps" as project, corinna at vinschen dot de as "email
address of person who approved request".
After that, checking out the project is done using
$ cvs -d :ext:@sourceware.org:/cvs/cygwin-apps co shutdown
Thanks,
Corinna
--
Corinna Vinschen Ple
2013/5/21 Corinna Vinschen:
> Uhm... I would prefer if we had the cygwin-specific tools in a single
> repository, if it's not asked too much. I'm sure we could add git
> access as well, if it's not already available.
I can continue to use CVS, no problem. No need to use git, just for
the sake of
On May 21 17:20, Frank Fesevur wrote:
> 2013/5/21 Corinna Vinschen:
> > I'm a bit reluctant as of the backward compatibility breakage. What
> > if somebody uses shutdown in a script? You know, starting a backup
> > in the evening and the last action of the script is to
2013/5/21 Corinna Vinschen:
> I'm a bit reluctant as of the backward compatibility breakage. What
> if somebody uses shutdown in a script? You know, starting a backup
> in the evening and the last action of the script is to hibernate the
> machine or something like that...
Tha
Fedin Pavel sent the following at Monday, May 20, 2013 10:00 AM
> And following the same logic we would need to teach our find.exe (already
> mentioned on this list) to understand Windows options instead of UNIX
> options...
FYI, Windows find = grep
c:\> find /?
Searches for a text string in a
On May 20 13:40, Frank Fesevur wrote:
> Hi Corinna,
>
> Since nobody made real objections about changing the short flag for
> hibernate from -h to -b to make room for -h for halt [1], I created a
> patch to change the shutdown program. The patch was created back in
> March, but
2013/5/20 Jeffrey Altman:
> I believe it is very important that the Cygwin shutdown not alter the
> meaning of command line parameters such that they are different from the
> Windows native version. The various options are already too confusing
> to remember. Typing the right optio
Greetings, Fedin Pavel!
> At the other hand, IMHO, Windows .bat scripts are never run from wihin
> bash, and vice versa, UNIX .sh scripts are never run from within cmd.exe...
That's a bold claim. If I run it down to underlying interpreter, I always run
all scripts from "cmd", be it .bat, .cmd, .
his list) to understand Windows
> options instead of UNIX options... Even further, in terminal case, why
> have Cygwin at all ? It is different from Windows command line and
> this is confusing... Kind regards.
Unlike the 'find' command, the shutdown command can leave the mac
On Mon, May 20, 2013 at 9:59 AM, Fedin Pavel wrote:
>
> At the other hand, IMHO, Windows .bat scripts are never run from wihin bash,
> and vice versa, UNIX .sh scripts are never run from within cmd.exe...
I do this.
Create a null (native, i.e. non-cygwin) program named #! and put it in
PATH. T
> I would be unhappy with this proposed change. The Windows
> "shutdown.exe" uses:
>
> 'h' for hibernate
> 'l' for logoff
> 's' for shutdown and halt
> 'r' for shutdown and restart
> 'g' for shutdown and
Frank,
I would be unhappy with this proposed change. The Windows
"shutdown.exe" uses:
'h' for hibernate
'l' for logoff
's' for shutdown and halt
'r' for shutdown and restart
'g' for shutdown and restart including register
Hi Corinna,
Since nobody made real objections about changing the short flag for
hibernate from -h to -b to make room for -h for halt [1], I created a
patch to change the shutdown program. The patch was created back in
March, but with all your work being done on cygwin64, your holiday and
myself
I've just updated the shutdown package to 1.8-1.
This is a copyright update in the first place, from GPLv2+ to GPLv3+.
All Windows 9x and NT4 considerations have been removed from the code.
I also changed the packaging method to cygport.
To update your installation, click on the "Inst
On 9/2/2011 11:26 AM, LMH wrote:
As an aside, why does which shutdown return /usr/bin/shutdown when the
shutdown app is located in /bin/shutdown? What value does the /usr part
of the path have in this context?
/bin and /usr/bin are the same thing by default under Cygwin. c:\cygwin
is
Using the full path was successful.
As an aside, why does which shutdown return /usr/bin/shutdown when the
shutdown app is located in /bin/shutdown? What value does the /usr part
of the path have in this context?
I suppose I should use force, but I never have anything running when I
run the
On Sep 1 14:51, LMH wrote:
> I have a bash script that runs rsync and I have been trying to add a
> command to shutdown the computer after the backup has finished
> running.
>
> I have added,
>
> shutdown -s now
>
> and also tried,
>
> shutdown -s 5
> shut
On 9/1/2011 2:51 PM, LMH wrote:
I have a bash script that runs rsync and I have been trying to add a command
to shutdown the computer after the backup has finished running.
I have added,
shutdown -s now
and also tried,
shutdown -s 5
shutdown -x now
shutdown -x 5
but the computer doesn&#
I have a bash script that runs rsync and I have been trying to add a
command to shutdown the computer after the backup has finished running.
I have added,
shutdown -s now
and also tried,
shutdown -s 5
shutdown -x now
shutdown -x 5
but the computer doesn't shut down. Running which shu
On Jun 15 09:02, ca...@gmx.de wrote:
> Hi,
>
> i use cygwin 1.7.5 on XP and try to reboot a win 2003 or win 2008 server with
> ssh and shutdown.exe.
>
> result of /usr/bin/shutdown.exe or ../windows/system32/shutdown.exe is
> shutdown: required privilege not held: Error 13
Hi,
i use cygwin 1.7.5 on XP and try to reboot a win 2003 or win 2008 server with
ssh and shutdown.exe.
result of /usr/bin/shutdown.exe or ../windows/system32/shutdown.exe is
shutdown: required privilege not held: Error 1300
The ssh-user has Admin rights and if connect with rdp this user can
On Feb 23 09:39, Fr?d?ric Bron wrote:
> What does this mean?
>
> $ win_shutdown
> WARNING!!! System is going down NOW
> shutdown: Couldn't shutdown: Error 53 The network path was not found.
>
> where win_shutdown just contains:
> shutdown -s now
On Mon, 23 Feb 2009 09:39:48 +0100
Frédéric Bron wrote:
> What does this mean?
>
> $ win_shutdown
> WARNING!!! System is going down NOW
> shutdown: Couldn't shutdown: Error 53 The network path was not found.
>
> where win_shutdown just contains:
> shutdown -s
What does this mean?
$ win_shutdown
WARNING!!! System is going down NOW
shutdown: Couldn't shutdown: Error 53 The network path was not found.
where win_shutdown just contains:
shutdown -s now
Frédéric Bron
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem re
On Dec 3, 2007 1:35 AM, <[EMAIL PROTECTED]> wrote:
> Hello,
>
>
> I would like to delete files when the Cygwin Server is shut down.
there is no server. you're thinking of an X server from the X/Cygwin project.
>
> Is there a way in cygwin to trap the shutdown
Hello,
I would like to delete files when the Cygwin Server is shut down.
Is there a way in cygwin to trap the shutdown event? (Ctrl-Alt-Backspace or
clicking on the Cygwin Exit Button).
Many thanks.
phiroc
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports
Ken Shaffer wrote:
I have just checked the source for the daemon() function and the
setsid executable. They
both call fork() and then setsid(). Do the console/rxvt process stick
after calling ssh -f
because file descriptors are left open? Can you suggest a strategy to
deal with this?
I'm not
I have just checked the source for the daemon() function and the setsid
executable. They
both call fork() and then setsid(). Do the console/rxvt process stick after
calling ssh -f
because file descriptors are left open? Can you suggest a strategy to deal with
this?
I'm not running ssh as a da
I originally reported this in October 2006
<http://cygwin.com/ml/cygwin/2006-10/msg00399.html>:
[Michael Hoffman]
When I log out of or shutdown my Windows login session, if I had a
background process that I started within a Win32 rxvt session, I get an
error that rxvt0 has not shu
Igor Peshansky wrote:
On Wed, 11 Oct 2006, Michael Hoffman wrote:
When I log out of or shutdown my Windows login session, if I had a
background process that I started within a Win32 rxvt session, I get an
error that rxvt0 has not shut down. For
example if I use ssh -f or run ssh in the
On Wed, 11 Oct 2006, Michael Hoffman wrote:
> When I log out of or shutdown my Windows login session, if I had a
> background process that I started within a Win32 rxvt session, I get an
> error that rxvt0 has not shut down. For
> example if I use ssh -f or run ssh in the back
When I log out of or shutdown my Windows login session, if I had a
background process that I started within a Win32 rxvt session, I get an
error that rxvt0 has not shut down. For
example if I use ssh -f or run ssh in the background using &, this
symptom manifests.
I can also s
On Sun, 2 Jul 2006, Maurício wrote:
> Igor Peshansky wrote:
> > On Sun, 2 Jul 2006, Maurício wrote:
> >
> > > Is it possible, using some cygwin functionality, to tell Windows to
> > > execute a command at shutdown? For instance, I would like to have:
Maurício wrote:
Hi,
Is it possible, using some cygwin functionality, to tell Windows to
execute a command at shutdown? For instance, I would like to have:
ipconfig.exe /release
executed everytime I shutdown Windows, since I need that to avoid
problems with my cable provider when using
Igor Peshansky wrote:
On Sun, 2 Jul 2006, Maurício wrote:
Hi,
Is it possible, using some cygwin functionality, to tell Windows to
execute a command at shutdown? For instance, I would like to have:
ipconfig.exe /release
executed everytime I shutdown Windows, since I need that to avoid
On Sun, 2 Jul 2006, Maurício wrote:
> Hi,
>
> Is it possible, using some cygwin functionality, to tell Windows to
> execute a command at shutdown? For instance, I would like to have:
>
> ipconfig.exe /release
>
> executed everytime I shutdown Windows, since I need
Hi,
Is it possible, using some cygwin functionality, to tell Windows to
execute a command at shutdown? For instance, I would like to have:
ipconfig.exe /release
executed everytime I shutdown Windows, since I need that to avoid
problems with my cable provider when using dual-boot. How
It seem that with recent snapshots the command
shutdown -x now
does not work any more.
I have done:
PC On
login as Administrator
click on Cygwin.bat link on the desktop
$ shutdown -x now (or shutdown -x 60)
but the bash window (Cygwin.bat) is not closed and a window
Christian Lanconelli (servizio) wrote:
> Hello world!,
> I need to shutdown my win 2000 O.S. at a specified time or "now".
> I'd like to use the command shutdown --force now but the system answer is
> that I don't have the necessary priviledge. How can I do? Have I
Hello world!,
I need to shutdown my win 2000 O.S. at a specified time or "now".
I'd like to use the command shutdown --force now but the system answer is
that I don't have the necessary priviledge. How can I do? Have I to activate
some service with cygrunsrv.exe for exempl
On Nov 11 12:42, Selmi Luko? wrote:
> hello
>
> my problem is that when i launch it with
> shutdown -f -s 15
> then it correctly terminates the windows session and everything but doesn't
> switch off computer, it will stay with message that it is safe to turn off
> comp
hello
my problem is that when i launch it with
shutdown -f -s 15
then it correctly terminates the windows session and everything but doesn't
switch off computer, it will stay with message that it is safe to turn off
computer
however when i shutdown windows manually (or for example when
Am I the only one experiencing this problem? No comments at all?
-- Gunnar
Gunnar Brading wrote:
The problem I am experiencing is that my ssh-agent won't die when
logging out or shutting down my Windows XP.
Instead I get the standard dialog box about "Cannot end this program"
with the option
The problem I am experiencing is that my ssh-agent won't die when
logging out or shutting down my Windows XP.
Instead I get the standard dialog box about "Cannot end this program"
with the option to end now, or cancel. Pusing the end now button
solves the problem, but I cannot find any reason for
> On Apr 29 09:27, Wheeler, Frederick W (Research) wrote:
> >
> > I have found that when I "Lock Computer" in Windows 2000 just after running
> > "shutdown --exitex 10"
> > then the computer does not shut down. Nothing happens. The command jus
On Apr 29 09:27, Wheeler, Frederick W (Research) wrote:
>
> I have found that when I "Lock Computer" in Windows 2000 just after running
> "shutdown --exitex 10" then the computer does not shut down. Nothing
> happens. The command just exits.
>
> When
With -x it works fine.
Thank you.
angelo.
--
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/
> Corinna Vinschen cygwin.com> writes:
>
> Too late. shutdown-1.6-1 should be on the mirrors soon.
>
> Corinna
>
shutdown-1.6-1 fixes the problem for me.
Regards & many thanks,
Christian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Pr
I've just updated the version of shutdown to 1.7-1.
This version adds the -x/--exitex option, which allows to use the
ExitWindowsEx function on Windows NT. This is important if shutdown is
supposed to poweroff on Windows 2000, since the InitiateSystemShutdown
implementation on Windows
On Apr 22 21:37, Angelo Graziosi wrote:
>
> I have tried shutdown-1.6-1. Now it seems to work in the sense that
>
>shutdown now
>shutdown 5
> ... 30
> etc.
>
> starts the procedure of shutdown, i.e. disconnets the user, saves the
> configur
I have tried shutdown-1.6-1. Now it seems to work in the sense that
shutdown now
shutdown 5
... 30
etc.
starts the procedure of shutdown, i.e. disconnets the user, saves the
configuration... . When it seems it is being to turn off the PC, Windows
says (in low resoultion
ID (LsaLookupNames returned 0xc073=STATUS_NONE_MAPPED)!
There is no user root, just a Cygwin group called root which maps to
the Administrators group.
> I´ll try the modified version of shutdown over the weekend and post the
> results.
Too late. shutdown-1.6-1 should be on the
I've just updated the version of shutdown to 1.6-1.
This version is a plain bugfix release which also adds a couple of
additional error messages to allow easier tracking down problems.
However, here's the release message for 1.5-1 again, for the people
who love to view replays:
On
> >
> > Same effect with shutdown-1.5-1
> > root is member of the admin group but does not map to the builtin
administrator.
>
> http://cygwin.com/ml/cygwin/2005-04/msg00977.html
>
> Corinna
>
I wanted to test if root lacks some of the system priviliges th
On Apr 22 13:22, Jason FU wrote:
> Jason FU ust.hk> writes:
> This one works. I forgot to use
>
> ./shutdown.exe ...
Thanks for testing.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
On Apr 22 13:14, Jason FU wrote:
> ===
> [EMAIL PROTECTED] ~/Shared Documents/C++
> $ ls -la shutdown.*
> -rw-r--r-- 1 tsfu None 10631 Apr 22 21:13 shutdown.c
> -rwxr-xr-x 1 tsfu None 24549 Apr 22 21:14 shutdown.
Jason FU ust.hk> writes:
>
> Corinna Vinschen cygwin.com> writes:
>
> >
> > On Apr 22 13:17, Corinna Vinschen wrote:
>
> >
> > I've created a patched version of shutdown which should give us some
> > hint why it doesn't work for y
Corinna Vinschen cygwin.com> writes:
>
> On Apr 22 13:17, Corinna Vinschen wrote:
>
> I've created a patched version of shutdown which should give us some
> hint why it doesn't work for you. The source is attached. Just call
> `make shutdown' and run th
On Apr 22 12:54, Christian Weinberger wrote:
> > > Same problem here with the previous version of shutdown:
> > > - cygwin 1.5.15
> > > - shutdown 1.4-1
> > > - XP Home SP2
> > > - connect via sshd or local on the desktop
> > >
> > >
> > Same problem here with the previous version of shutdown:
> > - cygwin 1.5.15
> > - shutdown 1.4-1
> > - XP Home SP2
> > - connect via sshd or local on the desktop
> >
> > Works fine from accounts that are in the admin group, but not for root.
> &
On Apr 22 13:17, Corinna Vinschen wrote:
> On Apr 22 10:59, Jason FU wrote:
> > Corinna Vinschen cygwin.com> writes:
> > > I know, that's why I was asking. I just ran shutdown-1.5-1 again on
> > > 2003 Server and it works fine for me. I tried it in local sess
On Apr 22 09:05, Christian Weinberger wrote:
> > Corinna Vinschen cygwin.com> writes:
> >
> > On Apr 21 23:52, Angelo Graziosi (D. Zanello) wrote:
> > > I am tried as Administrator:
> > >
> > >Administrator graziosi ~/Downloads/cygwin
>
> Corinna Vinschen cygwin.com> writes:
>
> On Apr 21 23:52, Angelo Graziosi (D. Zanello) wrote:
> > I am tried as Administrator:
> >
> >Administrator graziosi ~/Downloads/cygwin
> >$ shutdown now
> >WARNING!!! System is going down NOW
&
On Apr 21 23:52, Angelo Graziosi (D. Zanello) wrote:
> I am tried as Administrator:
>
>[EMAIL PROTECTED] ~/Downloads/cygwin
> $ shutdown now
>WARNING!!! System is going down NOW
>shutdown: Couldn't shutdown: Error 5 Accesso negato.
>
> (also "sh
I am tried as Administrator:
[EMAIL PROTECTED] ~/Downloads/cygwin
$ shutdown now
WARNING!!! System is going down NOW
shutdown: Couldn't shutdown: Error 5 Accesso negato.
(also "shutdown 5" does not work)
Thank you,
angelo.
[EMAIL PROTECTED]
--
Unsubscribe
I've just updated the version of shutdown to 1.5-1.
This version has some bugfixes plus two new features:
On Windows NT systems, shutdown now uses InitiateSystemShutdown to start
system shutdowns and reboots. This function has several advantages.
It allows to specify a time until shutdow
On May 11 17:47, Krzysztof Duleba wrote:
> Corinna Vinschen wrote:
>
> > On May 10 07:33, Egerton, James wrote:
> > > I've tried using the Cygwin shutdown-1.4 from an ssh session and it
> > > doesn't seem to do anything. The call to ExitWindowsEx doe
Corinna Vinschen wrote:
> On May 10 07:33, Egerton, James wrote:
> > I've tried using the Cygwin shutdown-1.4 from an ssh session and it
> > doesn't seem to do anything. The call to ExitWindowsEx doesn't
appear
> > to fail, but nothing happens after the &quo
On May 10 16:21, Michael F. March wrote:
> Let me amend my last email..
>
> Shutdown works if I am logged into the console..
Yes, of course, that makes perfectly sense, doesn't it? *cough, cough*
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwi
Let me amend my last email..
Shutdown works if I am logged into the console.. it has
nothing todo with VNC..
thanks!
Here is something kind of freaky.. If I am at the same time
logged into server that is running sshd using VNC, shutdown
through an SSH session, *DOES* work.
On May 10 07:33
Here is something kind of freaky.. If I am at the same time
logged into server that is running sshd using VNC, shutdown
through an SSH session, *DOES* work.
On May 10 07:33, Egerton, James wrote:
I've tried using the Cygwin shutdown-1.4 from an ssh session and it
doesn't seem to d
On May 10 07:33, Egerton, James wrote:
> I've tried using the Cygwin shutdown-1.4 from an ssh session and it
> doesn't seem to do anything. The call to ExitWindowsEx doesn't appear
> to fail, but nothing happens after the "WARNING!!!..." message is
> display
I've tried using the Cygwin shutdown-1.4 from an ssh session and it
doesn't seem to do anything. The call to ExitWindowsEx doesn't appear
to fail, but nothing happens after the "WARNING!!!..." message is
displayed. I have verified that the system ca
> Possible, but I suspect it's a problem on Jacek's machine.
>
> Jacek: Win2K SP2 is pretty ancient. Is it possible to try this on a
> later SP? (SP4 is the latest, and there have been numerous hotfixes
> since it was released.)
I've installed SP4 (had most of hotfixes already) but it didn't fix
Hannu E K Nevalainen wrote:
> $ g++ ShutdownTest.cpp -o ShutdownTest && ./ShutdownTest.exe
> HTTP/1.1 200 OK
> Date: Tue, 04 May 2004 14:02:39 GMT
> Server: Apache/1.3.27 (Unix) (Red-Hat/Linux)
> Last-Modified: Wed, 08 Jan 2003 23:11:55 GMT
[...]
>
> $ uname -a
> CYGWIN_NT-5.0 P450 1.5.10s(0.114
Hi,
> > Just kind of wondering if the apache is prematurely dropping the line when
> > it sees the FIN.
>
> Possible, but I suspect it's a problem on Jacek's machine.
Yep, that's most likely.
> Jacek: Win2K SP2 is pretty ancient. Is it possible to try this on a
> later SP? (SP4 is the latest,
Hi Dave,
> Just kind of wondering if the apache is prematurely dropping the line when
> it sees the FIN.
No it doesn't. Here is dump when connecting to example.org:
> 01:14:34.237976 win2k.3042 > example.org.80: S 3273603871:3273603871(0) win 16384
> (DF)
> 01:14:34.423719 example.org.80 > w
msg00013.html
>
> $ g++ ShutdownTest.cpp -o ShutdownTest && ./ShutdownTest.exe
> No output will mean that shutdown bug is present.
$ g++ ShutdownTest.cpp -o ShutdownTest && ./ShutdownTest.exe
HTTP/1.1 200 OK
Date: Tue, 04 May 2004 14:02:39 GMT
Server: Apache/1.3.27 (Unix) (Red-Ha
Dave Korn wrote:
Just kind of wondering if the apache is prematurely dropping the line when
it sees the FIN.
Possible, but I suspect it's a problem on Jacek's machine.
Jacek: Win2K SP2 is pretty ancient. Is it possible to try this on a
later SP? (SP4 is the latest, and there have been numerous h
> -Original Message-
> From: cygwin-owner On Behalf Of Larry Hall
> Sent: 04 May 2004 03:51
> At 10:19 PM 5/3/2004, you wrote:
>
> >Can somebody with Win2k box compile and run prog from my
> previous mail?
> >I would like to know if it behaves incorrectly only on my
> system, or on
> >
> -Original Message-
> From: cygwin-owner On Behalf Of Arash Partow
> Sent: 04 May 2004 07:37
> Hi,
>
> Just out of curiosity, if one were to do:
>
> shutdown(sck,SHUT_WR)
>
>
> which means as far as I understand it "stop all send reqs
> mad
Hi,
Just out of curiosity, if one were to do:
shutdown(sck,SHUT_WR)
which means as far as I understand it "stop all send reqs made to sck",
how would one reopen the sck so that you could make send reqs again?
Is that even possible or do you have to reestablish the connection
again fr
> I've tried your application and I'm not able to reproduce your problem.
> The shutdown call does not influence sending the buffered data apparently.
Thanks for info.
> I've tested with Cygwin 1.5.9 and with a recent snapshot on XP SP1.
> What's your system?
At 10:19 PM 5/3/2004, you wrote:
>> I've tried your application and I'm not able to reproduce your problem.
>> The shutdown call does not influence sending the buffered data apparently.
>
>Thanks for info.
>
>> I've tested with Cygwin 1.5.9 and with a
On May 2 00:07, Jacek Trzmiel wrote:
>
> Hi,
>
> $ cygcheck -cd cygwin
> Cygwin Package Information
> Package Version
> cygwin 1.5.9-1
>
> I found some unexpected behaviour of shutdown call. Here is example
> pro
Hi,
$ cygcheck -cd cygwin
Cygwin Package Information
Package Version
cygwin 1.5.9-1
I found some unexpected behaviour of shutdown call. Here is example
program to reproduce problem. It is supposed to send simple http
request to example.org
1 - 100 of 163 matches
Mail list logo
