>From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
>On Tue, 11 Mar 2003, Jason Tishler wrote:
>
>> [snip]
>> However, Cygwin setup.exe's cache should have all previous versions
>> installed including PostgreSQL unless one deletes them.
>Hence, the old
>> PostgreSQL version should still have bee
>Hello. This is my first mail to the list.
Well, for starters, you'll need to put a better subject line on your posts.
You might want to peruse
http://www.tuxedo.org/~esr/faqs/smart-questions.html for additional tips.
>I have this problem...
>... it [Redir v.2.1] really works. but when i close
>From: Max Bowsher [mailto:maxb@;ukf.net]
>
>Polley Christopher W <[EMAIL PROTECTED]> wrote:
>
>>> From: Max Bowsher [mailto:maxb@;ukf.net]
>>> I thought I might as well mention my download method:
>>> I wrote a little script to get a setup.in
>From: Max Bowsher [mailto:maxb@;ukf.net]
>I thought I might as well mention my download method:
>I wrote a little script to get a setup.ini file from a mirror,
>and then use
>Michael Chase's clean_setup.pl to make a list of URLs to get,
>and pass that
>to wget. I then invoke clean_setup.pl again
You might also try formail, which is included in the procmail package.
>From: Marcos Lorenzo
>
>I'm unable to fill some fields in mail header with ssmtp:
>
>When I run:
>
>marcos@MOZART ~$ echo "testing mail" | ssmtp -f
>administrador@mozart -F Administrador [EMAIL PROTECTED]
>
>
>I get the foll
Robert,
It's probably not your system that is infected -- Bugbear, like KLEZ, uses
addresses harvested from the infected system in spoofed "From" headers.
The only way I've been able to guess at the real identity for
bugbear-infected mail that I've received (from friends/family) is to search
thr
I don't use XP, so this is based on my NT/W2K/95/ME experience, but when
used in conjunction with '//host', 'name' should be the name that it is
shared as -- from the "Sharing..." menu option. Type \\JASON in your
Start->Run dialog -- that will show you the shares that are exposed.
HTH,
Chris
>
Thanks,
Chris
> -Original Message-
> From: Christopher Faylor [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, March 27, 2002 12:18 PM
> To: [EMAIL PROTECTED]
> Subject: Re: bash failed to initialize on telnet/rsh/rlogin server
>
> On Wed, Mar 27, 2002 at 09:05:20AM -0600
Thanks, David,
>This happened to me on NT4 when I upgraded to cygwin-1.3.10, and
was
>*not* using ntsec. Using ntsec fixed it. Is ntsec set early
enough
>for inetd? (And are you rebooting when making changes?) Does the
>inetd service have sufficient user rights
Bill,
The debug_printf statements get printed when you run your program under
strace. (see http://cygwin.com/faq/faq.html#TOC111 ) Also, here are some
excellent tips that cgf has given on strace and debugging cygwin1.dll:
http://www.cygwin.com/ml/cygwin/2000-11/msg01469.html (BTW, "google is yo
I'm trying to get inetd set up for telnet/rsh/rlogin on my machine and have
everything going up to the point that after login.exe gives the motd to the
telnet client, a dialog window pops up on the server titled "bash.exe -
Application Error" and says "The application failed to initialize properly
You wrote:
>At 01:45 PM 1/10/2002, Andrew DeFaria wrote:
>>Anyway, cron has no access to them. It's running under SYSTEM
>>account which has only access to publicly available net
drives, that
>>is, drives which are available w/o any form of authe
I think I've found the cause of this.
I'll summarize the problem, since this is an old thread:
when a Windows GUI IDE calls gcc or make, the process reports
"fhandler_base::dup: dup(unknown disk file) failed, handle 0, Win32 error 6"
and crashes.
The problem seems to occur when the [non-cygwin]
> -Original Message-
> From: Christopher Faylor [SMTP:[EMAIL PROTECTED]]
> On Fri, Dec 21, 2001 at 03:42:14PM +0100, Werner Tuchan wrote:
> >> Weird. The bytes after EOF are a mixture of NULs and 0xc0. Is 0xc0
> >> of special significance in Windows? Is your version of cygwin the
AFAIR
> > it. If you can, debugging Cygwin via gdb would be the best way to go.
> > Alternatively, if you can't do that, calling gcc indirectly through
> > strace in your IDE environment would provide some trace information
>
>
Here is a strace snippet right around the error's occurrence:
I've been looking into this problem myself, (see last month's thread
starting with http://www.cygwin.com/ml/cygwin/2001-11/msg01217.html )
and have gotten to this point: at the point where vfork is duplicating the
fhandler table and dup'ing open fh's it somehow isn't detecting that stdin
isn't c
Thanks, my apologies for asking a FAQ; I didn't see it on the list. I'll
give these methods a try and see how it goes.
Having done the make/make install from my source tree, do I have to repair
anything now? Where can I find more information on the rationale behind not
building in the src dire
Hello,
I'm trying to build cygwin(-1.3.5.3) with the debug symbols included. I
exported CFLAGS=-g, then did ./configure, make, and make install; but only
the .a libraries were built. Is there more info available about the
makefile targets in this package? The README doesn't mention it and it's
gcc 2.95.3-5 is the latest available from the cygwin mirrors, but I see from
the gcc 3.0.x build status (http://gcc.gnu.org/gcc-3.0/buildstat.html) that
it builds successfully on i[5|6]86-pc-cygwin. Are there any issues with
building 3.0 OOTB on cygwin? When will the cygwin package be released o
19 matches
Mail list logo
