Re: NTFS write-protect flag translation (tar? rsync?) only one-way?

2011-04-18 Thread Corinna Vinschen
On Apr  5 21:33, Larry Hall (Cygwin) wrote:
> On 4/5/2011 8:35 PM, Christian Gelinek wrote:
> >From: Cygwin On Behalf Of Larry Hall (Cygwin)
> >>On 4/5/2011 3:36 AM, Christian Gelinek wrote:
> >>>It appears that when tar reads files for adding to archives, it
> >>>correctly interprets the Windows-set "R" attribute, which is also seen by
> >>>ls under Cygwin. After extracting the files using tar though, only
> >>>Cygwin's ls command seems to be aware of the read-only attribute; the
> >>>attrib command (as well as Explorer and other Windows-apps) see and
> >>>handle the file as being writeable.
> >>
> >>The read-only attribute is a "Windows" thing.  Cygwin's utilities focus on
> >>supporting POSIXy/Linuxy ways of doing things.  You can't expect Cygwin's
> >>tools to manage all of Window's permission facilities in the same way as
> >>Windows does.  The read-only flag is one case where you'll see a divergence.
> >>If you need that flag set, you'll need your own wrapper to set it based on
> >>the POSIX (or ACL) permissions.  The read-only attribute really is quite
> >>anachronistic though IMO.  It conflicts with the more powerful ACLs.  If
> >>you have the option, it's better not to use that flag.
> >
> >IMO the behaviour is inconsistent if the flag is used/interpreted on one (the
> >read) operation but NOT being written/changed on the other (write) operation.
> >My approach would be either drop it completely or support it on both ends
> >(the preferred option).
> 
> Actually, the read-only attribute is not used by Cygwin to determine POSIX
> permissions.

Actually if it is set it is used to remove the write bits from the
permission bits in calls to stat.  However, since the DOS attributes
are only in the way in terms of POSIX permissions, it's never set
in calls to chmod.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: newlib and long-double question

2011-04-18 Thread Corinna Vinschen
On Apr 10 19:30, N. C. wrote:
> Exactly, I really need to be able to build Perl whose NV is a long
> double. And this was just one example that I gave. I honestly think it
> is worth it to have long double support in cygwin (to have those
> functions that are currently undefined), as it seems more and more
> clear that A) there is a use for them, and B) there are cases where it
> really is needed.
> 
> IIRC, the whole point of cygwin is to have a unix-like environment
> within a non-unix-like system, right? Does it not make sense to make
> the back bone (libc) that much mroe complete, furthur augmenting
> usability and compatibility?

The problem is not that anybody doubts that long double support is
useful, the problem is the simple lack of somebody actually volunteering
to do it.  We all have our plates full with other stuff to do.

So, if you're familiar with math stuff and you would like to see long
double support in newlib/Cygwin, there's nothing better than
contributing the code yourself.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: Syntax error in setfacl man page

2011-04-18 Thread Corinna Vinschen
On Apr 12 19:27, Fran wrote:
> I wrote:
> 
> > Sometime in the last few months, setfacl stopped accepting two colons (::)
> > after the keyword "other", as in this example:
> > 
> >   $ setfacl -s user::rw-,group::r--,other::r-- filename
> >   setfacl: illegal acl entries
> > 
> > But the setfacl(1) man page continues to show the invalid syntax:
> > 
> >   o[ther]::perm
> 
> Upon further investigation, it appears that it may be setfacl that is
> wrong rather than the man page.  According to the syntax summary given at:
> 
>   http://www.linuxmanpages.com/man1/setfacl.1.php
> 
> two colons are allowed after the keyword "other":

Thanks for the report.  I fixed that in CVS.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: what does this cygserver error mean?

2011-04-18 Thread Corinna Vinschen
On Apr 15 14:53, bob 295 wrote:
> I'm getting this error associated with shared memory and cygserver (sender is 
> the name of my process setting and loading the shared memory):
> 
>  begin error snip 
> 3 [main] sender 3684 transport_layer_pipes::connect: lost connection to 
> cygserver,  error = 2
>  end error snip =
> 
> Could someone point me to a place where this error is described?   Thanks.

error = 2 is the Win32 error ERROR_FILE_NOT_FOUND returned by the
CreateFile or WaitNamedPipe function when trying to connect to cygserver
via a named pipe.

Either Cygserver isn't running or it reached the maximum number of 
parallel client connections.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Memory leak in select.

2011-04-18 Thread Peter Rosin
Hi!

Using the following STC, I'm seeing what appears to be a memory
leak in select(2).

8<---(selectleak.c)-
#include 
#include 
#include 

int
main(void)
{
fd_set fdset;
struct timeval tv;

long flags = fcntl(0, F_GETFL);
fcntl(0, F_SETFL, flags | O_NONBLOCK);

for (;;) {
int res;
char buf[20];

FD_ZERO(&fdset);
FD_SET(0, &fdset);
tv.tv_sec = 1;
tv.tv_usec = 0;
res = select(1, &fdset, NULL, NULL, &tv);
if (res < 0)
exit(1);
if (!res)
continue;
res = read(0, buf, sizeof(buf));
if (res < 0)
exit(1);
}

return 0;
}
8<--

$ gcc -o selectleak selectleak.c
$ cat /dev/zero | ./selectleak

Note that "./selectleak < /dev/zero" does not trigger the leak for me (I haven't
seen the memory usage go up, so at least not as reliably).

An "strace -m malloc,select" has this:

  156   59281 [main] selectleak 8440 cygwin_select: 1, 0x23CCFC, 0x0, 0x0, 0x0
   64   59345 [main] selectleak 8440 calloc: (1, 44) = 49AF58, called by 
61002389
   63   59408 [main] selectleak 8440 calloc: (1, 12) = 49B018, called by 
61002389
  111   59519 [main] selectleak 8440 cygwin_select: to NULL, ms 
   62   59581 [main] selectleak 8440 cygwin_select: sel.always_ready 0
  138   59719 [select_pipe] selectleak 8440 peek_pipe: , ready for read: avail 
130892
  160   59879 [main] selectleak 8440 select_stuff::wait: woke up.  wait_ret 1.  
verifying
   57   59936 [main] selectleak 8440 set_bits: me 0x49AF58, testing fd 0 ()
   62   59998 [main] selectleak 8440 set_bits: ready 1
   62   60060 [main] selectleak 8440 select_stuff::wait: gotone 1
   61   60121 [main] selectleak 8440 select_stuff::wait: returning 0
   61   60182 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
routines
  104   60286 [main] selectleak 8440 free: (0x49B018), called by 0x610BC1EA
   65   60351 [main] selectleak 8440 peek_pipe: , already ready for read
   62   60413 [main] selectleak 8440 set_bits: me 0x49AF58, testing fd 0 ()
   62   60475 [main] selectleak 8440 set_bits: ready 1
   74   60549 [main] selectleak 8440 select_stuff::poll: returning 1
   61   60610 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
routines
   65   60675 [main] selectleak 8440 select_stuff::~select_stuff: deleting 
select records
   60   60735 [main] selectleak 8440 free: (0x49AF58), called by 0x610BC2A2
  108   60843 [main] selectleak 8440 calloc: (1, 44) = 49AF58, called by 
61002389
   64   60907 [main] selectleak 8440 calloc: (1, 12) = 49B018, called by 
61002389
  126   61033 [main] selectleak 8440 peek_pipe: , ready for read: avail 130892
   62   61095 [main] selectleak 8440 fhandler_base::ready_for_read: read_ready 
1, avail 1
   62   61157 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
routines
   61   61218 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
routines
   62   61280 [main] selectleak 8440 select_stuff::~select_stuff: deleting 
select records
   61   61341 [main] selectleak 8440 free: (0x49AF58), called by 0x610BC2A2
  226   61567 [main] selectleak 8440 cygwin_select: 1, 0x23CCFC, 0x0, 0x0, 0x0

Notice how the "calloc: (1, 12) = 49B018" is only freed once between the two
"cygwin_select: 1, 0x23CCFC, ..."-lines.

$ cygcheck -c cygwin gcc4
Cygwin Package Information
Package  VersionStatus
cygwin   1.7.9-1OK
gcc4 4.3.4-4OK

Cheers,
Peter

--
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



Re: listen socket / poll block

2011-04-18 Thread Corinna Vinschen
On Apr  6 18:19, Thomas Stalder wrote:
> Hello,
> 
> I made a small application that block poll function.
> 
> the result is :
> 
> before pthread_create
> after pthread_create
> before poll
> before shutdown socket
> after shutdown socket
> before close socket
> after close socket
> 
> 
> under linux the result is:
> 
> before pthread_create
> after pthread_create
> before poll
> before shutdown socket
> after shutdown socket
> after poll ret=1
> error accept failed: Invalid argument

First of all, thanks for the testcase.

It turns out that the semantics of Winsock's shutdown function are
different from the Linux implementation.  Not overly surprising, but it
makes trying to get the behaviour working the same way as on Linux
a bit awkward.

The problem is that in your scenario the shutdown function works fine on
Linux, and the subsequent call to accept fails because the socket has
been shutdown for reading.  On Winsock, the shutdown function *fails*,
the error code is "socket not connected".  Thus, even if Cygwin fakes
the results for shutdown to trigger the poll call, the accept call does
*not* fail.

I applied a fix which enforces the Linux behaviour.  Please give the
next developer snapshot from http://cygwin.com/snapshots/ a try.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: Memory leak in select

2011-04-18 Thread Peter Rosin
Den 2011-04-18 13:43 skrev Peter Rosin:
> Hi!
> 
> Using the following STC, I'm seeing what appears to be a memory
> leak in select(2).
> 
> 8<---(selectleak.c)-
> #include 
> #include 
> #include 
> 
> int
> main(void)
> {
>   fd_set fdset;
>   struct timeval tv;
> 
>   long flags = fcntl(0, F_GETFL);
>   fcntl(0, F_SETFL, flags | O_NONBLOCK);
> 
>   for (;;) {
>   int res;
>   char buf[20];
> 
>   FD_ZERO(&fdset);
>   FD_SET(0, &fdset);
>   tv.tv_sec = 1;
>   tv.tv_usec = 0;
>   res = select(1, &fdset, NULL, NULL, &tv);
>   if (res < 0)
>   exit(1);
>   if (!res)
>   continue;
>   res = read(0, buf, sizeof(buf));
>   if (res < 0)
>   exit(1);
>   }
> 
>   return 0;
> }
> 8<--
> 
> $ gcc -o selectleak selectleak.c
> $ cat /dev/zero | ./selectleak
> 
> Note that "./selectleak < /dev/zero" does not trigger the leak for me (I 
> haven't
> seen the memory usage go up, so at least not as reliably).
> 
> An "strace -m malloc,select" has this:
> 
>   156   59281 [main] selectleak 8440 cygwin_select: 1, 0x23CCFC, 0x0, 0x0, 0x0
>64   59345 [main] selectleak 8440 calloc: (1, 44) = 49AF58, called by 
> 61002389
>63   59408 [main] selectleak 8440 calloc: (1, 12) = 49B018, called by 
> 61002389
>   111   59519 [main] selectleak 8440 cygwin_select: to NULL, ms 
>62   59581 [main] selectleak 8440 cygwin_select: sel.always_ready 0
>   138   59719 [select_pipe] selectleak 8440 peek_pipe: , ready for read: 
> avail 130892
>   160   59879 [main] selectleak 8440 select_stuff::wait: woke up.  wait_ret 
> 1.  verifying
>57   59936 [main] selectleak 8440 set_bits: me 0x49AF58, testing fd 0 ()
>62   59998 [main] selectleak 8440 set_bits: ready 1
>62   60060 [main] selectleak 8440 select_stuff::wait: gotone 1
>61   60121 [main] selectleak 8440 select_stuff::wait: returning 0
>61   60182 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
> routines
>   104   60286 [main] selectleak 8440 free: (0x49B018), called by 0x610BC1EA
>65   60351 [main] selectleak 8440 peek_pipe: , already ready for read
>62   60413 [main] selectleak 8440 set_bits: me 0x49AF58, testing fd 0 ()
>62   60475 [main] selectleak 8440 set_bits: ready 1
>74   60549 [main] selectleak 8440 select_stuff::poll: returning 1
>61   60610 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
> routines
>65   60675 [main] selectleak 8440 select_stuff::~select_stuff: deleting 
> select records
>60   60735 [main] selectleak 8440 free: (0x49AF58), called by 0x610BC2A2
>   108   60843 [main] selectleak 8440 calloc: (1, 44) = 49AF58, called by 
> 61002389
>64   60907 [main] selectleak 8440 calloc: (1, 12) = 49B018, called by 
> 61002389
>   126   61033 [main] selectleak 8440 peek_pipe: , ready for read: avail 130892
>62   61095 [main] selectleak 8440 fhandler_base::ready_for_read: 
> read_ready 1, avail 1
>62   61157 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
> routines
>61   61218 [main] selectleak 8440 select_stuff::cleanup: calling cleanup 
> routines
>62   61280 [main] selectleak 8440 select_stuff::~select_stuff: deleting 
> select records
>61   61341 [main] selectleak 8440 free: (0x49AF58), called by 0x610BC2A2
>   226   61567 [main] selectleak 8440 cygwin_select: 1, 0x23CCFC, 0x0, 0x0, 0x0
> 
> Notice how the "calloc: (1, 12) = 49B018" is only freed once between the two
> "cygwin_select: 1, 0x23CCFC, ..."-lines.
> 
> $ cygcheck -c cygwin gcc4
> Cygwin Package Information
> Package  VersionStatus
> cygwin   1.7.9-1OK
> gcc4 4.3.4-4OK
> 
> Cheers,
> Peter

Arrrg, this is the program I actually used to generate that
strace (but the leak is present in both versions). Oh well,
sorry about that...

8<---(selectleak.c)-
#include 
#include 

int
main(void)
{
fd_set fdset;

long flags = fcntl(0, F_GETFL);
fcntl(0, F_SETFL, flags | O_NONBLOCK);

for (;;) {
int res;
char buf[20];

FD_ZERO(&fdset);
FD_SET(0, &fdset);
res = select(1, &fdset, NULL, NULL, NULL);
if (!res)
continue;
if (res < 0)
return 1;
res = read(0, buf, sizeof(buf));
if (!res)
break;
if (res < 0)
return 1;
}

return 0;
}
8<--

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubs

[ANNOUNCEMENT] Updated: mintty-0.9.7-1

2011-04-18 Thread Andy Koppe
mintty 0.9.7-1 is on its way to the Cygwin mirrors.

CHANGES
===
- Fixed crash when scrollback size is set to zero.
- NT4 support is officially gone. It had been broken since version
0.6.1 anyway, without anyone complaining.
- When the window is held open after the shell finished and no more
processes are attached, hitting Enter or Escape will now close the
window.
- Changed the optional Ctrl+Shift shortcut for closing the window from
Ctrl+Shift+Q to the more standard-compliant Ctrl+Shift+W.
- Added config file versions of command line options: Class, Hold,
Icon, Log, Title, Utmp, Window, X, Y.
- Multiple-choice settings are now written with named values rather
than integers, e.g. CursorType=block instead of the rather non-obvious
CursorType=0. Similarly, Boolean settings are written as 'no' or 'yes'
instead of 0 or 1. Integer values of course remain supported for
backward compatibility.
- String settings no longer have arbitrary length restrictions.
- Unknown settings and invalid values now trigger warnings.

DESCRIPTION
===
Mintty is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.

QUESTIONS
=
The mintty manual is installed as a manpage ('man mintty'). It's also
available at http://mintty.googlecode.com/svn/tags/0.9.7/docs/mintty.1.html.

Questions and comments can be sent to the mintty discussion group at
http://groups.google.com/group/mintty-discuss or the Cygwin mailing
list. Please use the issue tracker at
http://code.google.com/p/mintty/issues/list to report bugs or suggest
enhancements.



To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com web page.  This downloads setup.exe to
your system.  Then, run setup and answer all of the questions.

    *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

--
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



Re: Memory leak in select

2011-04-18 Thread Peter Rosin
Den 2011-04-18 14:23 skrev Peter Rosin:
> Den 2011-04-18 13:43 skrev Peter Rosin:
>> Hi!
>>
>> Using the following STC, I'm seeing what appears to be a memory
>> leak in select(2).
>>
> 8<---(selectleak.c)-
> #include 
> #include 
> 
> int
> main(void)
> {
>   fd_set fdset;
> 
>   long flags = fcntl(0, F_GETFL);
>   fcntl(0, F_SETFL, flags | O_NONBLOCK);
> 
>   for (;;) {
>   int res;
>   char buf[20];
> 
>   FD_ZERO(&fdset);
>   FD_SET(0, &fdset);
>   res = select(1, &fdset, NULL, NULL, NULL);
>   if (!res)
>   continue;
>   if (res < 0)
>   return 1;
>   res = read(0, buf, sizeof(buf));
>   if (!res)
>   break;
>   if (res < 0)
>   return 1;
>   }
> 
>   return 0;
> }
> 8<--

Ok, I'm taking a wild swing at this, and my guess is that the call
sel.cleanup () in cygwin_select prematurely zeros out the cleanup
member of the select_record. The call to sel.poll () then adds
"stuff" to the select_record that really should have been cleaned
up, but isn't since cleanup has already been executed and then
zapped (by select_stuff::cleanup).

But what do I know?

Cheers,
Peter

extern "C" int
cygwin_select (int maxfds, fd_set *readfds, fd_set *writefds, fd_set *exceptfds,
   struct timeval *to)
{
  select_stuff sel;
  fd_set *dummy_readfds = allocfd_set (maxfds);
  fd_set *dummy_writefds = allocfd_set (maxfds);
  fd_set *dummy_exceptfds = allocfd_set (maxfds);

  ...

  sel.cleanup ();  // Too early ???
  copyfd_set (readfds, r, maxfds);
  copyfd_set (writefds, w, maxfds);
  copyfd_set (exceptfds, e, maxfds);
  return timeout ? 0 : sel.poll (readfds, writefds, exceptfds);
}

--
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



Re: CYGWIN_NT-6.1-WOW64 on Windows 7: "died waiting for longjmp before initialization"?

2011-04-18 Thread Lonni J Friedman
Welcome to the club.  The only suggestion that I've been given for
this problem is to run 'rebaseall', which appears to fix it until it
happens again.

On Mon, Apr 18, 2011 at 8:02 AM, Sid Maxwell  wrote:
> I'm running CYGWIN_NT-6.1-WOW64 on a Lenovo ThinkPad W520 running
> Windows 7 Home Premium.  When using rvm to install [Ruby] 1.8.7.p334,
> during the "make" (compiling) phase, I see the following:
>
> ~> rvm --debug --trace install 1.8.7-p334
> --trace install 1.8.7-p334
>
> rvm 1.6.2 by Wayne E. Seguin (wayneeseg...@gmail.com)
> [https://rvm.beginrescueend.com/]
>
> + [[ -z '' ]]
> + export 'PS4=+ ${BASH_SOURCE##${rvm_path:-}} :
> ${FUNCNAME[0]:+${FUNCNAME[0]}()}  ${LINENO} > '
> + PS4='+ ${BASH_SOURCE##${rvm_path:-}} :
> ${FUNCNAME[0]:+${FUNCNAME[0]}()}  ${LINENO} > '
> + /scripts/cli : __rvm_parse_args()  709 > [[ -z '' ]]
> + /scripts/cli : __rvm_parse_args()  709 > [[ -n '' ]]
> .
> .
> .
> ++ /scripts/functions/utility : __rvm_run()  118 > command='make '
> ++ /scripts/functions/utility : __rvm_run()  119 >
> message='ruby-1.8.7-p334 - #compiling '
> ++ /scripts/functions/utility : __rvm_run()  121 > [[ -n
> ruby-1.8.7-p334 - #compiling  ]]
> ++ /scripts/functions/utility : __rvm_run()  122 > rvm_log
> 'ruby-1.8.7-p334 - #compiling '
> ++ /scripts/functions/logging : rvm_log()  14 > printf
> 'ruby-1.8.7-p334 - #compiling \n'
> ruby-1.8.7-p334 - #compiling
> ++ /scripts/functions/utility : __rvm_run()  125 > [[ 1 -gt 0 ]]
> ++ /scripts/functions/utility : __rvm_run()  126 > rvm_debug 'Executing: make 
> '
> ++ /scripts/functions/logging : rvm_debug()  15 > printf 'DEBUG:
> Executing: make \n'
> DEBUG: Executing: make
> ++ /scripts/functions/utility : __rvm_run()  128 > [[ -n ruby-1.8.7-p334 ]]
> ++ /scripts/functions/utility : __rvm_run()  129 >
> temp_log_path=/home/Sid/.rvm/log/ruby-1.8.7-p334
> ++ /scripts/functions/utility : __rvm_run()  134 >
> log=/home/Sid/.rvm/log/ruby-1.8.7-p334/make.log
> ++ /scripts/functions/utility : __rvm_run()  136 > [[ ! -d
> /home/Sid/.rvm/log/ruby-1.8.7-p334 ]]
> ++ /scripts/functions/utility : __rvm_run()  140 > [[ ! -f
> /home/Sid/.rvm/log/ruby-1.8.7-p334/make.log ]]
> +++ /scripts/functions/utility : __rvm_run()  142 > date '+%Y-%m-%d %H:%M:%S'
> ++ /scripts/functions/utility : __rvm_run()  142 > printf '[2011-04-18
> 09:52:34] make \n'
> ++ /scripts/functions/utility : __rvm_run()  144 > [[ 0 -gt 0 ]]
> ++ /scripts/functions/utility : __rvm_run()  148 > eval 'make '
>      7 [main] miniruby 2988 fork: child -1 - died waiting for longjmp
> before initialization, retry 10, exit code 0xC135, errno 11
> 1151962 [main] miniruby 2988 fork: child -1 - died waiting for longjmp
> before initialization, retry 10, exit code 0xC135, errno 11
> 2181188 [main] miniruby 2988 fork: child -1 - died waiting for longjmp
> before initialization, retry 10, exit code 0xC135, errno 11
> 3214648 [main] miniruby 2988 fork: child -1 - died waiting for longjmp
> before initialization, retry 10, exit code 0xC135, errno 11
> 4244470 [main] miniruby 2988 fork: child -1 - died waiting for longjmp
> before initialization, retry 10, exit code 0xC135, errno 11
> 5272498 [main] miniruby 2988 fork: child -1 - died waiting for longjmp
> before initialization, retry 10, exit code 0xC135, errno 11
> .
> .
> .
>
> These "died waiting for longjmp" messages continue until interrupted (^C).
>
> I've set the "compatibility" property for the cygwin.bat icon to
> Windows XP (Service Pack 3), with no change in behavior.  When I run
> the same rvm command on a Dell Inspiron 9200, running Windows XP/SP3
> and CYGWIN_NT-5.1, I do not see this behavior.
>
> Any assistance would be greatly appreciated.
>
> -+- Sid Maxwell
>
> P.S. Running "cygcheck -s -v -r > cygcheck.out" gets the following
> messages to stderr.  Is this normal, or part of the problem?
>
> ~> cygcheck -s -v -r > cygcheck.out
> /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 
> 5
> Access is denied.
> /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5
> Access is denied.
> /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5
> Access is denied.
> /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper':
> Win32 error 5
> Access is denied.
> /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5
> Access is denied.
> ~>

--
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



Re: CYGWIN_NT-6.1-WOW64 on Windows 7: "died waiting for longjmp before initialization"?

2011-04-18 Thread Eliot Moss

On 4/18/2011 11:05 AM, Lonni J Friedman wrote:

Welcome to the club.  The only suggestion that I've been given for
this problem is to run 'rebaseall', which appears to fix it until it
happens again.


To clarify a little: rebaseall should fix things until
cygwin programs are updated or added ...

Eliot Moss

--
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



Re: Memory leak in select

2011-04-18 Thread Christopher Faylor
On Mon, Apr 18, 2011 at 04:32:10PM +0200, Peter Rosin wrote:
>Den 2011-04-18 14:23 skrev Peter Rosin:
>> Den 2011-04-18 13:43 skrev Peter Rosin:
>>> Hi!
>>>
>>> Using the following STC, I'm seeing what appears to be a memory
>>> leak in select(2).
>>>
>> 8<---(selectleak.c)-
>> #include 
>> #include 
>> 
>> int
>> main(void)
>> {
>>  fd_set fdset;
>> 
>>  long flags = fcntl(0, F_GETFL);
>>  fcntl(0, F_SETFL, flags | O_NONBLOCK);
>> 
>>  for (;;) {
>>  int res;
>>  char buf[20];
>> 
>>  FD_ZERO(&fdset);
>>  FD_SET(0, &fdset);
>>  res = select(1, &fdset, NULL, NULL, NULL);
>>  if (!res)
>>  continue;
>>  if (res < 0)
>>  return 1;
>>  res = read(0, buf, sizeof(buf));
>>  if (!res)
>>  break;
>>  if (res < 0)
>>  return 1;
>>  }
>> 
>>  return 0;
>> }
>> 8<--
>
>Ok, I'm taking a wild swing at this, and my guess is that the call
>sel.cleanup () in cygwin_select prematurely zeros out the cleanup
>member of the select_record. The call to sel.poll () then adds
>"stuff" to the select_record that really should have been cleaned
>up, but isn't since cleanup has already been executed and then
>zapped (by select_stuff::cleanup).
>
>But what do I know?

How does sel.poll add "stuff" that should be cleaned up?  That function
only looks for bits to set.

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



Re: Memory leak in select

2011-04-18 Thread Christopher Faylor
On Mon, Apr 18, 2011 at 11:24:41AM -0400, Christopher Faylor wrote:
>On Mon, Apr 18, 2011 at 04:32:10PM +0200, Peter Rosin wrote:
>>Den 2011-04-18 14:23 skrev Peter Rosin:
>>> Den 2011-04-18 13:43 skrev Peter Rosin:
 Hi!

 Using the following STC, I'm seeing what appears to be a memory
 leak in select(2).

>>> 8<---(selectleak.c)-
>>> #include 
>>> #include 
>>> 
>>> int
>>> main(void)
>>> {
>>> fd_set fdset;
>>> 
>>> long flags = fcntl(0, F_GETFL);
>>> fcntl(0, F_SETFL, flags | O_NONBLOCK);
>>> 
>>> for (;;) {
>>> int res;
>>> char buf[20];
>>> 
>>> FD_ZERO(&fdset);
>>> FD_SET(0, &fdset);
>>> res = select(1, &fdset, NULL, NULL, NULL);
>>> if (!res)
>>> continue;
>>> if (res < 0)
>>> return 1;
>>> res = read(0, buf, sizeof(buf));
>>> if (!res)
>>> break;
>>> if (res < 0)
>>> return 1;
>>> }
>>> 
>>> return 0;
>>> }
>>> 8<--
>>
>>Ok, I'm taking a wild swing at this, and my guess is that the call
>>sel.cleanup () in cygwin_select prematurely zeros out the cleanup
>>member of the select_record. The call to sel.poll () then adds
>>"stuff" to the select_record that really should have been cleaned
>>up, but isn't since cleanup has already been executed and then
>>zapped (by select_stuff::cleanup).
>>
>>But what do I know?
>
>How does sel.poll add "stuff" that should be cleaned up?  That function
>only looks for bits to set.

Also since select() can allocate a persistent thread you can't expect that
the number of allocs will always be equal to the number of frees.  There
could be some allocation of space for thread bookkeeping.

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



Shared library error when invoking 'octave'

2011-04-18 Thread Paul Cantalupo
Hello,

When I invoked 'octave', I got the following error:

/usr/bin/octave-3.4.0.exe: error while loading shared libraries: ?:
cannot open shared object file: No such file or directory


So I did a cygcheck and got this:

(3866) sirius-pipas:~ $ cygcheck octave-3.4.0.exe
Found: C:\cygwin\bin\octave-3.4.0.exe
Found: C:\cygwin\bin\octave-3.4.0.exe
C:\cygwin\bin\octave-3.4.0.exe
  C:\cygwin\bin\cygoctinterp-3-4-0.dll
C:\cygwin\bin\cygoctave-3-4-0.dll
  C:\cygwin\bin\cygcruft-3-4-0.dll
C:\cygwin\bin\cyggcc_s-1.dll
  C:\cygwin\bin\cygwin1.dll
C:\WINDOWS\system32\ADVAPI32.DLL
  C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
  C:\WINDOWS\system32\RPCRT4.dll
C:\WINDOWS\system32\Secur32.dll
C:\cygwin\bin\cyggfortran-3.dll
C:\cygwin\bin\cygstdc++-6.dll
  C:\cygwin\bin\cygreadline7.dll
C:\cygwin\bin\cygncursesw-10.dll
C:\WINDOWS\system32\USER32.dll
  C:\WINDOWS\system32\GDI32.dll
  C:\cygwin\bin\cygfftw3-3.dll
  C:\cygwin\bin\cygfftw3f-3.dll
  C:\cygwin\bin\cygqrupdate-0.dll
C:\cygwin\bin\cygGL-1.dll
  C:\cygwin\bin\cygX11-xcb-1.dll
  C:\cygwin\bin\cygX11-6.dll
C:\cygwin\bin\cygxcb-1.dll
  C:\cygwin\bin\cygXau-6.dll
  C:\cygwin\bin\cygXdmcp-6.dll
  C:\cygwin\bin\cygXext-6.dll
  C:\cygwin\bin\cygxcb-glx-0.dll
C:\cygwin\bin\cygGLU-1.dll
C:\cygwin\bin\cygz.dll
C:\cygwin\bin\cygfontconfig-1.dll
  C:\cygwin\bin\cygexpat-1.dll
  C:\cygwin\bin\cygfreetype-6.dll
  C:\cygwin\bin\cygiconv-2.dll
C:\cygwin\bin\cyghdf5-6.dll
cygcheck: track_down: could not find cygblas-0.dll
cygcheck: track_down: could not find cyglapack-0.dll
cygcheck: track_down: could not find cygblas-0.dll
cygcheck: track_down: could not find cyglapack-0.dll
cygcheck: track_down: could not find cygblas-0.dll
cygcheck: track_down: could not find cyglapack-0.dll
cygcheck: track_down: could not find cyglapack-0.dll



Seems I am missing some .dll files. What is the best way to fix this?

Thank you,

Paul

--
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



SFTP with a key pair fails, SSH works fine

2011-04-18 Thread Jason Schamp

I've struggled with this for weeks. I'm using Cygwin v1.7.5 or v1.7.7 and see 
the same behavior. SSH with or
without a key pair will work flawlessly every time. SFTP with a password will 
work fine, but SFTP with a key
pair will fail every time. The server thinks the publickey is accepted and then 
calls the SFTP subsystem... but it
will disconnect a few seconds later. sftp-server.exe has the privileged server 
and domain users in the NTFS
security and the privilege server has modify rights. It really looks like it 
should be working. Any ideas?

Here is the debug code from the client when attempting to SFTP with a key pair:

SCHAMJI@OHCSCXXE85061MT /cygdrive/c
$ sftp -v -v -v -i /cygdrive/c/id_rsa RISF01P@SDC01DERFNPA01S
OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to SDC01DERFNPA01S [10.16.107.184] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/cygdrive/c/id_rsa" as a RSA1 public key
debug2: key_type_from_name: unknown key type '-BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-END'
debug3: key_read: missing keytype
debug1: identity file /cygdrive/c/id_rsa type 1
debug1: identity file /cygdrive/c/id_rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4
debug1: match: OpenSSH_5.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.8
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "sdc01derfnpa01s" from file
"/home/SCHAMJI/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in 
file/home/SCHAMJI/.ssh/known_hosts:6
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs:
ssh-rsa-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hell
man-group-exchange-s
roup1-sha1
debug2: kex_parse_kexinit:
ssh-rsa-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@open
ssh.com,ecdsa-sha2-nistp38
v...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ecdsa-sha2-nistp256,ec
dsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes
192-cbc,aes256-cbc,arc
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes
192-cbc,aes256-cbc,arc
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-
96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-
96,hmac-md5-96
debug2: kex_parse_kexinit: none,z...@openssh.com,zlib
debug2: kex_parse_kexinit: none,z...@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-h
ellman-group1-sha
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes
192-cbc,aes256-cbc,arc
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes
192-cbc,aes256-cbc,arc
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-
96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-
96,hmac-md5-96
debug2: kex_parse_kexinit:

Re: poll function don't release all windows handle / possible memory leak

2011-04-18 Thread Corinna Vinschen
On Apr 18 11:35, Thomas Stalder wrote:
> Hello,
> 
> I have found that poll function don't release all windows handle (with
> network socket) and generate memory leak.

That's actually a pthread problem in conjunction with select (poll only
calls select under the hood).  I applied a fix to CVS.  Thanks for the
testcase!


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Octave Plotting, Invoking Octave

2011-04-18 Thread Doug Pace

Installed cygwin with gnuplot, X11, and octave.

Octave will not run the 'sombrero' demo plot.

Have removed c:\cygwin and reinstalled; have attempted previous releases 
of cygwin and octave.

Yes, I needed to use ash and do
$ ./rebaseall
to get startx to work.

Now octave no longer opens, no error messages are issued just returns to 
the shell prompt.


This is on XP sp 3. 


Thanks for any help,

Doug

-- in octave /usr/share/octave/3.4.0/m/plot/__gnuplot_get_var__.m
the line 
   str = strcat(str {:}); -latest version

   str = strcat(str, {:});   -previous version
  previous version is correct.

screen capture follows:
**

$ octave

GNU Octave, version 3.4.0

Copyright (C) 2011 John W. Eaton and others.

This is free software; see the source code for copying conditions.

There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or

FITNESS FOR A PARTICULAR PURPOSE.  For details, type `warranty'.



Octave was configured for "i686-pc-cygwin".



Additional information about Octave is available at http://www.octave.org.



Please contribute if you find this software useful.

For more information, visit http://www.octave.org/help-wanted.html



Read http://www.octave.org/bugs.html to learn how to submit bug reports.



For information about changes from previous versions, type `news'.



octave:1> who

Variables in the current scope:



ans



octave:2> x = 1:1:10

x =



   123456789   10



octave:3> y = x .* x

y =



1 4 9162536496481   100



octave:4> sombrero

 0 [main] octave-3.4.0 3668 C:\cygwin\bin\octave-3.4.0.exe: *** 
fatal error - couldn't release memory 0x18D01000(61440) for 
'\\?\C:\cygwin\lib\octave\3.4.0\oct\i686-pc-cygwin\cellfun.oct' 
alignment, Win32 error 487


Stack trace:

Frame Function  Args

00229828  6102796B  (00229828, , , )

00229B18  6102796B  (6117EC60, 8000, , 61180977)

0022AB48  61004F1B  (611A7F74, 18D01000, F000, 6124A284)

End of stack trace

 0 [main] octave 3664 fork: child 3668 - died waiting for dll 
loading, errno 11


error: popen2: process creation failed -- Resource temporarily unavailable

error: called from:

error:   /usr/share/octave/3.4.0/m/plot/__gnuplot_open_stream__.m at 
line 30, column 44


error:   /usr/share/octave/3.4.0/m/plot/__gnuplot_drawnow__.m at line 
72, column 19


octave:5



$ cygcheck -c cygwin x11 gnuplot octave

Cygwin Package Information

Package  VersionStatus

cygwin   1.7.9-1OK

gnuplot  4.4.0-1OK

octave   3.4.0-3OK





--
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



Re: what does this cygserver error mean?

2011-04-18 Thread bob 295
(I'm in digest mode on this list so I can't thread my response easily.)

The cygserver is setup to run as a Windows service.  As far as I can tell the 
cygserver is running when the error occurs.   What isn't clear from your 
response is what causes the named pipe to cygserver to get created?  What 
tears it down?

In my test the sequence of each Send/Receive/Reply message pass involves these 
steps:  
1) the sender creates the shared memory and then attaches to for the purpose 
of writing a message.
2) The receiver gets passed the shmid (via a named pipe) and attaches for the 
purpose of reading the message.   
3) The receiver will respond by writing into same shared memory area upon 
which it will detach.

I have a script which is repeatedly sending a 1k message (up to 10 times).  
The error isn't consistently happening but when it does it appears to happen 
on the first message pass.

Thanks again in advance for all your help.

bob


on Apr 15 14:53, bob 295 wrote:
> I'm getting this error associated with shared memory and cygserver (sender 
is 
> the name of my process setting and loading the shared memory):
> 
>  begin error snip 
> 3 [main] sender 3684 transport_layer_pipes::connect: lost connection to 
> cygserver,  error = 2
>  end error snip =
> 
> Could someone point me to a place where this error is described?   Thanks.

error = 2 is the Win32 error ERROR_FILE_NOT_FOUND returned by the
CreateFile or WaitNamedPipe function when trying to connect to cygserver
via a named pipe.

Either Cygserver isn't running or it reached the maximum number of 
parallel client connections.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: strftime trouble with %z

2011-04-18 Thread Corinna Vinschen
On Apr 14 11:09, Peter Rosin wrote:
> Hi!
> 
> I'm getting somewhat troublesome output from the below STC.
> It seems as if gmtime mucks with something, or that
> localtime is not filling in everything it needs to?

Thanks for the testcase!

Actually gmtime mucks with something.  It changes global timezone
information for no good reason.  I fixed that in CVS.


Thanks for the report,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: Memory leak in select

2011-04-18 Thread Peter Rosin
Den 2011-04-18 17:28 skrev Christopher Faylor:
> On Mon, Apr 18, 2011 at 11:24:41AM -0400, Christopher Faylor wrote:
>> On Mon, Apr 18, 2011 at 04:32:10PM +0200, Peter Rosin wrote:
>>> Den 2011-04-18 14:23 skrev Peter Rosin:
 Den 2011-04-18 13:43 skrev Peter Rosin:
> Hi!
>
> Using the following STC, I'm seeing what appears to be a memory
> leak in select(2).
>
 8<---(selectleak.c)-
 #include 
 #include 

 int
 main(void)
 {
fd_set fdset;

long flags = fcntl(0, F_GETFL);
fcntl(0, F_SETFL, flags | O_NONBLOCK);

for (;;) {
int res;
char buf[20];

FD_ZERO(&fdset);
FD_SET(0, &fdset);
res = select(1, &fdset, NULL, NULL, NULL);
if (!res)
continue;
if (res < 0)
return 1;
res = read(0, buf, sizeof(buf));
if (!res)
break;
if (res < 0)
return 1;
}

return 0;
 }
 8<--
>>>
>>> Ok, I'm taking a wild swing at this, and my guess is that the call
>>> sel.cleanup () in cygwin_select prematurely zeros out the cleanup
>>> member of the select_record. The call to sel.poll () then adds
>>> "stuff" to the select_record that really should have been cleaned
>>> up, but isn't since cleanup has already been executed and then
>>> zapped (by select_stuff::cleanup).
>>>
>>> But what do I know?
>>
>> How does sel.poll add "stuff" that should be cleaned up?  That function
>> only looks for bits to set.

I shouldn't have included the strace, and I shouldn't have guessed about
the cause of the problem without verifying my claims. Sorry about that.
But for the record the included strace snippet is reoccurring like that
many many times (the address of the allocation that isn't freed is
moving).  Further evidence; the STC leaks 1 MB every 3 seconds on my
computer, that just can't be right.

I have probably just read the code wrong, and I did say it was a wild
swing. So please ignore my feeble guesses as to what the cause might be
and take it from the symptoms instead. You have been provided with a STC,
and I have certainly done a fair share in cornering the bug my coming up
with that STC. You should be aware that the STC was NOT the first thing
I tried and it was NOT the first thing I thought was wrong when I
observed a leak in one of my "real" programs.

> Also since select() can allocate a persistent thread you can't expect that
> the number of allocs will always be equal to the number of frees.  There
> could be some allocation of space for thread bookkeeping.

Have you tried to invoke the program like I wrote in the original message
(i.e. cat /dev/zero | ./selectleak) before making sweeping statements like
that?

Cheers,
Peter

--
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



Re: what does this cygserver error mean?

2011-04-18 Thread Corinna Vinschen
On Apr 18 13:34, bob 295 wrote:
> (I'm in digest mode on this list so I can't thread my response easily.)
> 
> The cygserver is setup to run as a Windows service.  As far as I can tell the 
> cygserver is running when the error occurs.   What isn't clear from your 
> response is what causes the named pipe to cygserver to get created?  What 
> tears it down?

Every single request to cygserver is basically a closed operation.
A function call like shmget opens the pipe, writes a request block,
reads the reply from cygserver and closes the pipe.

> 
> In my test the sequence of each Send/Receive/Reply message pass involves 
> these 
> steps:  
> 1) the sender creates the shared memory and then attaches to for the purpose 
> of writing a message.
> 2) The receiver gets passed the shmid (via a named pipe) and attaches for the 
> purpose of reading the message.   
> 3) The receiver will respond by writing into same shared memory area upon 
> which it will detach.

Wouldn't it be simpler to use POSIX shared memory for that?  shm_open
allows to specify a named shared memory which all applications of a
project can share without having to use IPC to transmit the name (aka
"shmid") of the shared region.  On Cygwin it also drops the requirement
to use cygserver.

> I have a script which is repeatedly sending a 1k message (up to 10 times).  
> The error isn't consistently happening but when it does it appears to happen 
> on the first message pass.

If you could create a very simple, self-contained testscase in plain C,
I'd take a look.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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



Re: Octave Plotting, Invoking Octave

2011-04-18 Thread marco atzeri
On Mon, Apr 18, 2011 at 6:25 PM, Doug Pace  wrote:
> Installed cygwin with gnuplot, X11, and octave.
>
> Octave will not run the 'sombrero' demo plot.
>
> Have removed c:\cygwin and reinstalled; have attempted previous releases of
> cygwin and octave.
> Yes, I needed to use ash and do
>            $ ./rebaseall
> to get startx to work.
>
> Now octave no longer opens, no error messages are issued just returns to the
> shell prompt.
>
> This is on XP sp 3.
> Thanks for any help,

Doug,
rebaseall seems to break octave on WinXP. I already noted it on 1.7.9
and on some snapshots.

Workaround.
- reinstall octave
- downgrade cygwin from 1.7.9-1 to 1.7.8-1

At least on my WinXP SP3 it works.

>
> Doug

Marco

>
> -- in octave /usr/share/octave/3.4.0/m/plot/__gnuplot_get_var__.m
>    the line                    str = strcat(str {:});     -latest
> version
>                   str = strcat(str, {:});   -previous version
>      previous version is correct.
>
> screen capture follows:
> **
>
> $ octave
>
> GNU Octave, version 3.4.0
>
> Copyright (C) 2011 John W. Eaton and others.
>
> This is free software; see the source code for copying conditions.
>
> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
>
> FITNESS FOR A PARTICULAR PURPOSE.  For details, type `warranty'.
>
>
>
> Octave was configured for "i686-pc-cygwin".
>
>
>
> Additional information about Octave is available at http://www.octave.org.
>
>
>
> Please contribute if you find this software useful.
>
> For more information, visit http://www.octave.org/help-wanted.html
>
>
>
> Read http://www.octave.org/bugs.html to learn how to submit bug reports.
>
>
>
> For information about changes from previous versions, type `news'.
>
>
>
> octave:1> who
>
> Variables in the current scope:
>
>
>
> ans
>
>
>
> octave:2> x = 1:1:10
>
> x =
>
>
>
>   1 2 3 4 5 6 7 8 9 10
>
>
>
> octave:3> y = x .* x
>
> y =
>
>
>
>    1     4     9    16    25    36    49    64    81   100
>
>
>
> octave:4> sombrero
>
>     0 [main] octave-3.4.0 3668 C:\cygwin\bin\octave-3.4.0.exe: *** fatal
> error - couldn't release memory 0x18D01000(61440) for
> '\\?\C:\cygwin\lib\octave\3.4.0\oct\i686-pc-cygwin\cellfun.oct' alignment,
> Win32 error 487
>
> Stack trace:
>
> Frame     Function  Args
>
> 00229828  6102796B  (00229828, , , )
>
> 00229B18  6102796B  (6117EC60, 8000, , 61180977)
>
> 0022AB48  61004F1B  (611A7F74, 18D01000, F000, 6124A284)
>
> End of stack trace
>
>     0 [main] octave 3664 fork: child 3668 - died waiting for dll loading,
> errno 11
>
> error: popen2: process creation failed -- Resource temporarily unavailable
>
> error: called from:
>
> error:   /usr/share/octave/3.4.0/m/plot/__gnuplot_open_stream__.m at line
> 30, column 44
>
> error:   /usr/share/octave/3.4.0/m/plot/__gnuplot_drawnow__.m at line 72,
> column 19
>
> octave:5
>
>
>
> $ cygcheck -c cygwin x11 gnuplot octave
>
> Cygwin Package Information
>
> Package              Version        Status
>
> cygwin               1.7.9-1        OK
>
> gnuplot              4.4.0-1        OK
>
> octave               3.4.0-3        OK
>
>
>
>
>
> --
> 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
>
>

--
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



Re: strftime trouble with %z

2011-04-18 Thread Peter Rosin
Den 2011-04-18 21:13 skrev Corinna Vinschen:
> On Apr 14 11:09, Peter Rosin wrote:
>> Hi!
>>
>> I'm getting somewhat troublesome output from the below STC.
>> It seems as if gmtime mucks with something, or that
>> localtime is not filling in everything it needs to?
> 
> Thanks for the testcase!
> 
> Actually gmtime mucks with something.  It changes global timezone
> information for no good reason.  I fixed that in CVS.

I'm looking forward to the next snapshot!

> Thanks for the report,
> Corinna

Thanks for the fix,
Peter

--
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



Re: Shared library error when invoking 'octave'

2011-04-18 Thread marco atzeri
On Mon, Apr 18, 2011 at 5:35 PM, Paul Cantalupo wrote:
> Hello,
>
> When I invoked 'octave', I got the following error:
>
> /usr/bin/octave-3.4.0.exe: error while loading shared libraries: ?:
> cannot open shared object file: No such file or directory
>
>
> So I did a cygcheck and got this:
>
> (3866) sirius-pipas:~ $ cygcheck octave-3.4.0.exe
> Found: C:\cygwin\bin\octave-3.4.0.exe
> Found: C:\cygwin\bin\octave-3.4.0.exe
> C:\cygwin\bin\octave-3.4.0.exe
>  C:\cygwin\bin\cygoctinterp-3-4-0.dll
>    C:\cygwin\bin\cygoctave-3-4-0.dll
>      C:\cygwin\bin\cygcruft-3-4-0.dll
>        C:\cygwin\bin\cyggcc_s-1.dll
>          C:\cygwin\bin\cygwin1.dll
>            C:\WINDOWS\system32\ADVAPI32.DLL
>              C:\WINDOWS\system32\KERNEL32.dll
>                C:\WINDOWS\system32\ntdll.dll
>              C:\WINDOWS\system32\RPCRT4.dll
>                C:\WINDOWS\system32\Secur32.dll
>        C:\cygwin\bin\cyggfortran-3.dll
>        C:\cygwin\bin\cygstdc++-6.dll
>      C:\cygwin\bin\cygreadline7.dll
>        C:\cygwin\bin\cygncursesw-10.dll
>        C:\WINDOWS\system32\USER32.dll
>          C:\WINDOWS\system32\GDI32.dll
>      C:\cygwin\bin\cygfftw3-3.dll
>      C:\cygwin\bin\cygfftw3f-3.dll
>      C:\cygwin\bin\cygqrupdate-0.dll
>    C:\cygwin\bin\cygGL-1.dll
>      C:\cygwin\bin\cygX11-xcb-1.dll
>      C:\cygwin\bin\cygX11-6.dll
>        C:\cygwin\bin\cygxcb-1.dll
>          C:\cygwin\bin\cygXau-6.dll
>          C:\cygwin\bin\cygXdmcp-6.dll
>      C:\cygwin\bin\cygXext-6.dll
>      C:\cygwin\bin\cygxcb-glx-0.dll
>    C:\cygwin\bin\cygGLU-1.dll
>    C:\cygwin\bin\cygz.dll
>    C:\cygwin\bin\cygfontconfig-1.dll
>      C:\cygwin\bin\cygexpat-1.dll
>      C:\cygwin\bin\cygfreetype-6.dll
>      C:\cygwin\bin\cygiconv-2.dll
>    C:\cygwin\bin\cyghdf5-6.dll
> cygcheck: track_down: could not find cygblas-0.dll
> cygcheck: track_down: could not find cyglapack-0.dll
> cygcheck: track_down: could not find cygblas-0.dll
> cygcheck: track_down: could not find cyglapack-0.dll
> cygcheck: track_down: could not find cygblas-0.dll
> cygcheck: track_down: could not find cyglapack-0.dll
> cygcheck: track_down: could not find cyglapack-0.dll

cyglapack-0.dll and cygblas-0.dll are not on your path.

I guess you redefined the PATH by yourself removing
/usr/lib/lapack

that the two scripts in /etc/profile.d are supposed to define.


$ cygcheck -l liblapack0
/etc/profile.d/lapack0.csh
/etc/profile.d/lapack0.sh
/usr/lib/lapack/cygblas-0.dll
/usr/lib/lapack/cyglapack-0.dll

>
> Seems I am missing some .dll files. What is the best way to fix this?
>
> Thank you,
>
> Paul
>

--
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



emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread Tim Daneliuk
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all.  Xemacs works
fine.

Previously, I was able to work around this by falling back to a 
previous version of emacs, but this too seems broken now.

Ideas?
-- 

Tim Daneliuk
tun...@tundraware.com

--
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



Re: emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread marco atzeri
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk  wrote:
> This has happened the last few times I did an upgrade with setup.exe.
> emacs, emacs-nox, and emacs -nw will not start at all.  Xemacs works
> fine.
>
> Previously, I was able to work around this by falling back to a
> previous version of emacs, but this too seems broken now.
>
> Ideas?

http://cygwin.com/problems.html

> --
> 
> Tim Daneliuk

--
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



Re: emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread Ken Brown

On 4/18/2011 4:02 PM, marco atzeri wrote:

On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk  wrote:

This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all.  Xemacs works
fine.

Previously, I was able to work around this by falling back to a
previous version of emacs, but this too seems broken now.

Ideas?


http://cygwin.com/problems.html


While we're waiting for a full problem report, I'll make my best guess: 
 The OP needs to run rebaseall.


Ken

--
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



Re: emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread Christopher Faylor
On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
>On 4/18/2011 4:02 PM, marco atzeri wrote:
>> On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk  wrote:
>>> This has happened the last few times I did an upgrade with setup.exe.
>>> emacs, emacs-nox, and emacs -nw will not start at all.  Xemacs works
>>> fine.
>>>
>>> Previously, I was able to work around this by falling back to a
>>> previous version of emacs, but this too seems broken now.
>>>
>>> Ideas?
>>
>> http://cygwin.com/problems.html
>
>While we're waiting for a full problem report, I'll make my best guess: 
>  The OP needs to run rebaseall.

And possibly also a "cygcheck /usr/bin/emacs.exe" right?

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



Re: emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread Ken Brown

On 4/18/2011 4:30 PM, Christopher Faylor wrote:

On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:

On 4/18/2011 4:02 PM, marco atzeri wrote:

On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk  wrote:

This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all.  Xemacs works
fine.

Previously, I was able to work around this by falling back to a
previous version of emacs, but this too seems broken now.

Ideas?


http://cygwin.com/problems.html


While we're waiting for a full problem report, I'll make my best guess:
  The OP needs to run rebaseall.


And possibly also a "cygcheck /usr/bin/emacs.exe" right?


Yes, but without the ".exe".  (/usr/bin/emacs is a symlink that resolves 
to either emacs-X11.exe or emacs-nox.exe.)


Ken

--
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



Re: emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread Christopher Faylor
On Mon, Apr 18, 2011 at 04:36:09PM -0400, Ken Brown wrote:
>On 4/18/2011 4:30 PM, Christopher Faylor wrote:
>> On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
>>> On 4/18/2011 4:02 PM, marco atzeri wrote:
 On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk  wrote:
> This has happened the last few times I did an upgrade with setup.exe.
> emacs, emacs-nox, and emacs -nw will not start at all.  Xemacs works
> fine.
>
> Previously, I was able to work around this by falling back to a
> previous version of emacs, but this too seems broken now.
>
> Ideas?

 http://cygwin.com/problems.html
>>>
>>> While we're waiting for a full problem report, I'll make my best guess:
>>>   The OP needs to run rebaseall.
>>
>> And possibly also a "cygcheck /usr/bin/emacs.exe" right?
>
>Yes, but without the ".exe".  (/usr/bin/emacs is a symlink that resolves 
>to either emacs-X11.exe or emacs-nox.exe.)

Ah, right.  In that case, it would probably be best to do:

cygcheck /usr/bin/emacs-X11.exe
cygcheck /usr/bin/emacs-nox.exe

I don't think cygcheck can resolve a symlink.

(I'm not near a Windows machine to test right now)

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



Re: How is setup.ini generated these days?

2011-04-18 Thread Jens Schweikhardt
On Sun, Apr 17, 2011 at 01:35:01PM -0400, Christopher Faylor wrote:
...
# setup.ini is generated by a program called "upset".  The current sources
# are not available to the public since the program is not intended for
# "roll-your-own-setup.ini" and the program is not something that I want
# to receive patches for or questions about.
# 
# Older versions of the program are probably not kicking around out they
# are not supported here.
# 
# If you want to generate a setup.ini use genini.  If you find bugs, then
# proposed patches will be thoughtfully considered as long as they aren't
# band-aids.

For starters, the categories have apparently changed. The latest setup.exe
does not have Comm and Sound, but has gained Accessibility and Security.


--- genini.orig 2011-04-18 23:28:30.0 +0200
+++ genini  2011-04-18 23:32:56.0 +0200
@@ -289,9 +289,9 @@
 
 BEGIN {
 my @cats = qw'
- Admin Archive Audio Base Comm Database Devel Doc Editors Games
+ Accessibility Admin Archive Audio Base Database Devel Doc Editors Games
  Gnome Graphics Interpreters KDE Libs Mail Math Mingw Net Perl
- Publishing Python Science Shells Sound System Text Utils Web X11
+ Publishing Python Science Security Shells System Text Utils Web X11
  _obsolete _PostInstallLast
  ';
 @main::categories{map {lc $_} @cats} = @cats;

Regards,

Jens
-- 
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)

--
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



Re: emacs No Longer Works After A Cygwin Upgrade

2011-04-18 Thread Tim Daneliuk

On 4/18/2011 3:27 PM, Ken Brown wrote:

On 4/18/2011 4:02 PM, marco atzeri wrote:

On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:

This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.

Previously, I was able to work around this by falling back to a
previous version of emacs, but this too seems broken now.

Ideas?


http://cygwin.com/problems.html


While we're waiting for a full problem report, I'll make my best guess: The OP 
needs to run rebaseall.

Ken


I already tried this.  No go.
--

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/


--
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



Re: Memory leak in select

2011-04-18 Thread Peter Rosin
Den 2011-04-18 17:24 skrev Christopher Faylor:
> On Mon, Apr 18, 2011 at 04:32:10PM +0200, Peter Rosin wrote:
>> Den 2011-04-18 14:23 skrev Peter Rosin:
>>> Den 2011-04-18 13:43 skrev Peter Rosin:
 Hi!

 Using the following STC, I'm seeing what appears to be a memory
 leak in select(2).

>>> 8<---(selectleak.c)-
>>> #include 
>>> #include 
>>>
>>> int
>>> main(void)
>>> {
>>> fd_set fdset;
>>>
>>> long flags = fcntl(0, F_GETFL);
>>> fcntl(0, F_SETFL, flags | O_NONBLOCK);
>>>
>>> for (;;) {
>>> int res;
>>> char buf[20];
>>>
>>> FD_ZERO(&fdset);
>>> FD_SET(0, &fdset);
>>> res = select(1, &fdset, NULL, NULL, NULL);
>>> if (!res)
>>> continue;
>>> if (res < 0)
>>> return 1;
>>> res = read(0, buf, sizeof(buf));
>>> if (!res)
>>> break;
>>> if (res < 0)
>>> return 1;
>>> }
>>>
>>> return 0;
>>> }
>>> 8<--
>>
>> Ok, I'm taking a wild swing at this, and my guess is that the call
>> sel.cleanup () in cygwin_select prematurely zeros out the cleanup
>> member of the select_record. The call to sel.poll () then adds
>> "stuff" to the select_record that really should have been cleaned
>> up, but isn't since cleanup has already been executed and then
>> zapped (by select_stuff::cleanup).
>>
>> But what do I know?
> 
> How does sel.poll add "stuff" that should be cleaned up?  That function
> only looks for bits to set.

I added syscall to the strace mask and that places the leak in read(2)
instead. But as stated previously, just look at the symptoms instead and
ignore my finger-pointing.

(I was fooled by the fact that the leak was after the sel.cleanup call,
but my limited experience with strace made me miss the fact that read(2)
was entered before the leak. So, I mistakedly placed the leak in the only
part left in cygwin_select, namely sel.poll)

Cheers,
Peter

--
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



Cygwin Setup Available Download Sites is empty

2011-04-18 Thread Michael Loreto
I want to install Cygwin on Windows 7, but I'm stuck on Choose Download 
Site. There are no sites on the Available Download Sites list. I've 
tried copying URLs from the list of Mirror Sites and adding them to the 
Available Download Sites, but that doesn't work either. I get "Unable to 
get setup.ini from " I can download the files directly with 
no problem. It's just Setup that can't do it. I have tried downloading 
the setup files and doing the setup from a local directory (Downloads), 
but that didn't work either.  I get "nothing needs to be installed". 
I've also tried reinstall and uninstall. Same thing. This has to be 
something really simple...


--
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



cygwin ssh server error 5

2011-04-18 Thread andyman2011

Im trying to setup an ssh server and once i get to writing in my password it
doesnt let me.. 

warning:creating the user andy failed reason:system error 5 has occured

access is denied

please enter a password for new user 
please be sure that this password matches the password rules given on your
system... bla bla 

Im an ametuer, and dont understand this. What am i doing wrong and how do i
fix this??? thanks
-- 
View this message in context: 
http://old.nabble.com/cygwin-ssh-server-error-5-tp31429649p31429649.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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