Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

On Jan 25 19:55, DePriest, Jason R. wrote: > mkgroup_l_d:S-1-5-32-545:10545: > > A Google search for > GID 10545 > implies that this is 'Domain Users'. > > Not that it should make a big difference, but you might want to edit > your /etc/group and change > mkgroup_l_d:S-1-5-32-545:10545: > to > Do

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

--- Corinna Vinschen <[EMAIL PROTECTED]> ha scritto: > Actually the SID S-1-5-32-545 is the Users group on > the local machine. > If you need the SID for the Domain Users group you > have to retrieve > it using `mkgroup -d -g "Domain Users"', which gives > you something > like this: > > $ mkgr

mount nfs ?

Hello, I would like to mount a remote directory in cygwin. When I issue a command like this mount : /cygdrive/d/ it allways tells me mount: /cygdrive/d/: Invalid argument. What's wrong here? Is it even possible with cygwin to mount nfs-directories? thanks, stephan -- Unsubscribe info:

PING ntsec [was RE: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2]

On 26 January 2007 09:34, Corinna Vinschen wrote: > once in a while? It's outdated (Dave?) Hi, haven't forgotten but got a bit overloaded. I'll try and finish a first draft this weekend. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http

Re: mount nfs ?

On Jan 26 12:56, [EMAIL PROTECTED] wrote: > Hello, > I would like to mount a remote directory in cygwin. When I issue a > command like this > > mount : /cygdrive/d/ > > it allways tells me > > mount: /cygdrive/d/: Invalid argument. > > What's wrong here? Is it even possible with cygwin to mou

Re: PING ntsec [was RE: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2]

On Jan 26 12:00, Dave Korn wrote: > On 26 January 2007 09:34, Corinna Vinschen wrote: > > > > once in a while? It's outdated (Dave?) > > Hi, haven't forgotten but got a bit overloaded. I'll try and finish a first > draft this weekend. Cool, thanks! Corinna -- Corinna Vinschen

Re: gettext 0.14.5 - some warnings on compiling

Eric Blake-1 wrote: > > > It depends on whether the warning was masking a bug or not. But you are > better off reporting such bugs to the upstream maintainers - oftentimes, > that warning indicates a true bug where someone has compiled on Linux and > used wchar_t when they should have used win

Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

On Fri, 26 Jan 2007, Marco Atzeri wrote: > --- Corinna Vinschen <[EMAIL PROTECTED]> ha scritto: . Thanks. > > Actually the SID S-1-5-32-545 is the Users group on > > the local machine. > > If you need the SID for the Domain Users group you > > have to

Re: gettext 0.14.5 - some warnings on compiling

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to -VASKO- on 1/26/2007 5:54 AM: > > So, to whom I should report about these warnings to get skilled suggestions > for fast fixing or confirmations for safely ignoring it? Anybody can really > help ? Thanks a lot. > When building a package

���� ������ ����� ����� ������ �������� ���� ������ �� ���� ���� �

ßá Çááì äÝÓß Ýíå...ãæÞÚ ÔÇãá ÇÍÏË ÇÓØæÇäÇÊ ÇáÔÑÍ æÇáÊÚáíã æ ÇáÈÑÇãÌ æ ÇáÇáÚÇÈ ÇÓØæÇäÇÊ ááÞÑÂä ÇáßÑíã ÈÕæÊ ÇßËÑ ãä 50 ÞÇÑìÁ ãä ÇáãÔÇåíÑ ÇáÂä ÊÓÊØíÚ ÊÑßíÈ æäÏæÒ ÝíÓÊÇ Ã

[ANNOUNCEMENT] Updated: cygwin-1.5.24-1

I've made a new version of the Cygwin DLL and associated utilities available for download. This is mainly a bug fix release and eventually the last 1.5 release of Cygwin. For the changes, see below. *** NOTE *** This is also the very last release which officially support

Re: Endianess not declared

Hi, Dave Korn wrote: On 21 January 2007 06:54, Kovarththanan Rajaratnam wrote: It seems I got things mixed up. The ieeefp.h that was apparently included is located in /usr/include/machine/ieeefp.h and not usr/include/ieeefp.h. Got it, I see now. Well, this clause should fire: /tmp $ cat

Re: [ANNOUNCEMENT] Updated: cygwin-1.5.24-1

Corinna Vinschen wrote, On 26.1.2007 15:35: > I've made a new version of the Cygwin DLL and associated utilities > available for download. > > This is mainly a bug fix release and eventually the last 1.5 release > of Cygwin. For the changes, see below. > Last? Does this mean you have plans for

Re: ED9217

Good day, Viazzgra $1, 80 Ciazzlis $3, 00 Levizztra $3, 35 http://www.printeryml.*com ( Important ! Remove "*" ) -- were discussing magical methods of aging themselves and bluffing their way into the Triwizard Tournament. Todays not bad... outside all morning, said Ron, who was running his

Re: ED9217

Good day, Viazzgra $1, 80 Ciazzlis $3, 00 Levizztra $3, 35 http://www.printeryml.*com ( Important ! Remove "*" ) -- were discussing magical methods of aging themselves and bluffing their way into the Triwizard Tournament. Todays not bad... outside all morning, said Ron, who was running his

Re: [ANNOUNCEMENT] Updated: cygwin-1.5.24-1

On Fri, Jan 26, 2007 at 06:38:35PM +0100, V??clav Haisman wrote: >Corinna Vinschen wrote, On 26.1.2007 15:35: >>I've made a new version of the Cygwin DLL and associated utilities >>available for download. >> >>This is mainly a bug fix release and eventually the last 1.5 release of >>Cygwin. For th

grep -P segfault

Can anyone reproduce this? This is on a fairly small Cygwin installation on WinXP, last updated 4 days ago. $ echo hello | grep -P '\n' hello ? hello ? hello 4 [main] grep 3280 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core d

Re: grep -P segfault

Mike Brown wrote: > Can anyone reproduce this? Reproduced on cygwin 1.5.22 with grep 2.5.1 $ echo hello | grep -P '\n' hello hello hello Segmentation fault (core dumped) Alex -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.

Re: grep -P segfault

--- Mike Brown wrote: > Can anyone reproduce this? > > This is on a fairly small Cygwin installation on > WinXP, last updated 4 days > ago. > > $ echo hello | grep -P '\n' > hello > > ? hello > > ? hello > 4 [main] grep 3280 _cygtls::handle_exceptions: > Error while dumping state >

Re: grep -P segfault

Alexander Sotirov wrote: > Reproduced on cygwin 1.5.22 with grep 2.5.1 Frodak wrote: > I get the same problem. If you redirect the output to > a file, the "hello" is printed and then about 128k of > NULL characters are printed before it crashes. Great! Thanks guys. Do I need to do anything els

Re: grep -P segfault

--- Mike Brown wrote: > Alexander Sotirov wrote: > > Reproduced on cygwin 1.5.22 with grep 2.5.1 > > Frodak wrote: > > I get the same problem. If you redirect the > output to > > a file, the "hello" is printed and then about 128k > of > > NULL characters are printed before it crashes. > > > G

Re: grep -P segfault

Mike Brown wrote: > Can anyone reproduce this? > > This is on a fairly small Cygwin installation on WinXP, last updated 4 days > ago. > > $ echo hello | grep -P '\n' > hello > > ? hello > > ? hello > 4 [main] grep 3280 _cygtls::handle_exceptions: Error while dumping state > (probably c

Re: grep -P segfault

Brian Dessent wrote: > Right before calling memchr, beg points to the first byte in the string > "hello\n", end points to the \n character, and so does buflim. Thus > (buflim - end) is zero, and memchr returns NULL. From there match_size > is miscalculated and from there it's all downhill. The

Re: grep -P segfault

--- Brian Dessent wrote: > Brian Dessent wrote: > > > Right before calling memchr, beg points to the > first byte in the string > > "hello\n", end points to the \n character, and so > does buflim. Thus > > (buflim - end) is zero, and memchr returns NULL. > From there match_size > > is miscalcu

Re: hang when using pthread and fork in 1.5.23-1 and snapshot 20070118, and now 1.5.24-1.

Hello, I tried the latest release of cygwin1.dll (1.5.24-1) and it still is hanging in the same way. I've tried to debug further with gdb, but so far I haven't got any useful information out of gdb. I'll keep trying to get some debug information, but if any one else can reproduce the pro