Postgresql installation problems.

Postgresql installation problems.

[Kurt Roeckx]

I'm trying to install postgresql on windows XP.  I did follow the
documentation, and installed ipc-deamon (cygipc).  I'm using
ipc-daemon 1.13-2

I have a problem getting the ipc-deamon to work.  When I run
ipc-daemon --install-as-service, it doesn't want to start.

When I use cygrunsrv and tell that the args are --service.  In
that case it runs for about 5 seconds and then dies and I can't
find a reason.

If I then change the args to --service --debug-level=2, it seems
to stay running.

If I then try my initdb, it hangs itself creating the template1
database, like in case the ipc-daemon isn't running.

Note that the documentation says that you have to run initdb
before you start the ipc-daemon service, but I thought that that
is wrong and initdb requires the service too.

I've also tried just running "ipc-daemon &", but that didn't seem
to help either, it always hangs creating the database.

Anybody seen this problem before, and now how to get it to work?


Kurt


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

Hi again!

I have some new problems with sshd on Windows 2000.
(all latest cygwin packages from today)

I try to login on my Win 2000 machine from my Linux machine. Works fine
so far. (Thanks for your recent help!)
But: if I use RSA authentication with "authorized_keys" to get on the
cygwin machine it still works but I don't have network/sockets - the
windows socket interface cannot be initialized?!

If I remove "authorized_keys" and login via password it works again.
Strange, or?

Here's a copy and paste:

tino@tinux:~ > ssh tinont
Tino@tinont's password:
Last login: Sat Nov 16 18:12:09 2002 from tinux.tino-lange.de
Fanfare!!!
You are successfully logged in to this server!!!

Tino@TINONT ~
$ ping tinux

Ping tinux [192.168.1.1] mit 32 Bytes Daten:

Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64

Ping-Statistik fr 192.168.1.1:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms

Tino@TINONT ~
$ cat .ssh/identity.pub > .ssh/authorized_keys

Tino@TINONT ~
$ chmod 644 .ssh/authorized_keys

Tino@TINONT ~
$ logout
Connection to tinont closed.

tino@tinux:~ > ssh tinont
Last login: Sat Nov 16 18:12:51 2002 from tinux.tino-lange.de
Fanfare!!!
You are successfully logged in to this server!!!

Tino@TINONT ~
$ ping tinux
Fehler bei der Initialisierung der Windows-Socketsschnittstelle.
Fehlercode 0.

Tino@TINONT ~
$ rm .ssh/authorized_keys

Tino@TINONT ~
$ logout
Connection to tinont closed.

tino@tinux:~ > ssh tinont
Last login: Sat Nov 16 18:12:51 2002 from tinux.tino-lange.de
Fanfare!!!
You are successfully logged in to this server!!!

Tino@TINONT ~
$ ping tinux

Ping tinux [192.168.1.1] mit 32 Bytes Daten:

Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64

Ping-Statistik fr 192.168.1.1:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms

Tino@TINONT ~
$

Do you have an idea?
Thanks!

Tino

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Postgresql installation problems.

[Jason Tishler]

Kurt,

Note I do not have access to XP Home or Pro, so there is a limit to how
much I can help.

Any XP users successfully running PostgreSQL?  If so, please post your
experiences to the list.  I'm especially interested in XP Home, since I
assume that XP Pro will be the same as NT/2000.

On Sat, Nov 16, 2002 at 05:44:58PM +0100, Kurt Roeckx wrote:
> I'm trying to install postgresql on windows XP.

Please see the following thread:

    http://archives.postgresql.org/pgsql-cygwin/2002-11/msg00037.php

It may be helpful to you -- especially if you are using XP Home which is
uncharted territory.

> I have a problem getting the ipc-deamon to work.  When I run
> ipc-daemon --install-as-service, it doesn't want to start.

What version of Cygwin are you using?  An older version (IIRC, 1.3.13),
had issues with running ipc-daemon as a service.  Please upgrade to the
latest Cygwin, if necessary.

> If I then try my initdb, it hangs itself creating the template1
> database, like in case the ipc-daemon isn't running.

The above implies that you are not using the latest Cygwin PostgreSQL,
please upgrade to the latest.

> Note that the documentation says that you have to run initdb
> before you start the ipc-daemon service, but I thought that that
> is wrong and initdb requires the service too.

The above "typo" has been recently corrected:

    http://www.tishler.net/jason/software/postgresql/postgresql-7.2.3.README

> I've also tried just running "ipc-daemon &", but that didn't seem
> to help either, it always hangs creating the database.

Please read the README regarding what clean up is necessary when
switching the account under which ipc-daemon runs.

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

infinite loop in rm

[William A. Hoffman]

I saw some mention of this problem here:
http://www.cygwin.com/ml/cygwin/2002-07/msg00147.html

Is there a fix for this that works, or will be incorporated 
into a future version of cygwin?  I looked in the FAQ and
saw nothing about it.   I have some nightly scripts that clean
some directories, and if I leave a shell open in one of the
directories, the scripts just run forever trying to remove
the directory.

-Bill


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: infinite loop in rm

[Joe Buehler]

William A. Hoffman wrote:

> I saw some mention of this problem here:
> http://www.cygwin.com/ml/cygwin/2002-07/msg00147.html
> 
> Is there a fix for this that works, or will be incorporated 
> into a future version of cygwin?  I looked in the FAQ and
> saw nothing about it.   I have some nightly scripts that clean
> some directories, and if I leave a shell open in one of the
> directories, the scripts just run forever trying to remove
> the directory.

I am using the following patch to unlink() on a version of Cygwin that
is several months old.  It does nothing unless there is a directory
named .cygdel at the root of the drive holding the file to be deleted.
In that case, it moves the file there before trying to delete it.

Make sure you make the directory mode 777 when you create it...

Works for me -- I think I posted this to the list but may be wrong.

Joe Buehler

Index: src/winsup/cygwin/syscalls.cc
===================================================================
RCS file: /cvs/src/src/winsup/cygwin/syscalls.cc,v
retrieving revision 1.214
diff -u -r1.214 syscalls.cc
--- src/winsup/cygwin/syscalls.cc	2 Jul 2002 03:06:32 -0000	1.214
+++ src/winsup/cygwin/syscalls.cc	8 Aug 2002 16:38:12 -0000
@@ -142,6 +142,23 @@
  	SetFileAttributes (win32_name, (DWORD) win32_name & ~FILE_ATTRIBUTE_READONLY);
      }

+  // attempt to rename before deleting
+  char *basename;
+  basename = strrchr(win32_name, '\\');
+  if (basename && *++basename) {
+    const char *rootdir = win32_name.root_dir();
+    if (rootdir) {
+      const char *s = strrchr(rootdir, '\\');
+      if (s && !s[1]) {
+	char newname[MAX_PATH + 12];
+	__small_sprintf(newname, "%s.cygdel\\%s", rootdir, basename);
+	if (MoveFile(win32_name.get_win32(), newname)) {
+	  win32_name.check(newname, PC_SYM_NOFOLLOW | PC_FULL);
+	}
+      }
+    }
+  }
+
    DWORD lasterr;
    lasterr = 0;
    for (int i = 0; i < 2; i++)




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Postgresql installation problems.

[Kurt Roeckx]

On Mon, Nov 18, 2002 at 03:49:47PM -0500, Jason Tishler wrote:
> 
> Any XP users successfully running PostgreSQL?  If so, please post your
> experiences to the list.  I'm especially interested in XP Home, since I
> assume that XP Pro will be the same as NT/2000.

I'm using XP Pro.

> On Sat, Nov 16, 2002 at 05:44:58PM +0100, Kurt Roeckx wrote:
> > I'm trying to install postgresql on windows XP.
> 
> Please see the following thread:
> 
>     http://archives.postgresql.org/pgsql-cygwin/2002-11/msg00037.php

Oh, didn't know about that list yet ...

> > I have a problem getting the ipc-deamon to work.  When I run
> > ipc-daemon --install-as-service, it doesn't want to start.
> 
> What version of Cygwin are you using?  An older version (IIRC, 1.3.13),
> had issues with running ipc-daemon as a service.  Please upgrade to the
> latest Cygwin, if necessary.

I'm using 1.3.15.  It's a fresh install of a few days ago.

> > If I then try my initdb, it hangs itself creating the template1
> > database, like in case the ipc-daemon isn't running.
> 
> The above implies that you are not using the latest Cygwin PostgreSQL,
> please upgrade to the latest.

I'm still using 7.2.3-1, I guess I downloaded it just before
7.2.3-2 came out ...

It seems it should just give a error instead of using all CPU.
Anything else changed?

> > Note that the documentation says that you have to run initdb
> > before you start the ipc-daemon service, but I thought that that
> > is wrong and initdb requires the service too.
> 
> The above "typo" has been recently corrected:

I knew about it, I've hit the same problem over a year ago.  I
wonder why it never got corrected. :)

> Please read the README regarding what clean up is necessary when
> switching the account under which ipc-daemon runs.

I did remove the files in /tmp.

I tried about everything I could think of.


Kurt


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Postgresql installation problems.

[Jason Tishler]

Kurt,

On Tue, Nov 19, 2002 at 01:40:41AM +0100, Kurt Roeckx wrote:
> On Mon, Nov 18, 2002 at 03:49:47PM -0500, Jason Tishler wrote:
> > Any XP users successfully running PostgreSQL?  If so, please post
> > your experiences to the list.  I'm especially interested in XP Home,
> > since I assume that XP Pro will be the same as NT/2000.
> 
> I'm using XP Pro.

Hmm...I assumed XP Pro would be the same as NT/2000.  I guess it is time
to debug why ipc-daemon is not working for you under XP Pro.

> It seems it should just give a error instead of using all CPU.

Yes.

> Anything else changed?

Nothing on the PostgreSQL side.  However, it is built against cygipc
1.13-2 instead of 1.11-1.  See the cygipc ChangeLog for the details.

> I tried about everything I could think of.

You may want to try the pgsql-cygwin@postgresql.org mailing list.  IIRC,
there are users there using XP.

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1252; format=flowed, Size: 2699 bytes --]

Hi Cygwin-List!

Just discoverd that the same problem exists with ".ssh/authorized_keys2".

Can someone reproduce the problem?

Cheers,

Tino

---------------------

Tino Lange wrote:
> Hi again!
> 
> I have some new problems with sshd on Windows 2000.
> (all latest cygwin packages from today)
> 
> I try to login on my Win 2000 machine from my Linux machine. Works fine
> so far. (Thanks for your recent help!)
> But: if I use RSA authentication with "authorized_keys" to get on the
> cygwin machine it still works but I don't have network/sockets - the
> windows socket interface cannot be initialized?!
> 
> If I remove "authorized_keys" and login via password it works again.
> Strange, or?
> 
> Here's a copy and paste:
> 
> tino@tinux:~ > ssh tinont
> Tino@tinont's password:
> Last login: Sat Nov 16 18:12:09 2002 from tinux.tino-lange.de
> Fanfare!!!
> You are successfully logged in to this server!!!
> 
> Tino@TINONT ~
> $ ping tinux
> 
> Ping tinux [192.168.1.1] mit 32 Bytes Daten:
> 
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> 
> Ping-Statistik fr 192.168.1.1:
>     Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
> Ca. Zeitangaben in Millisek.:
>     Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms
> 
> Tino@TINONT ~
> $ cat .ssh/identity.pub > .ssh/authorized_keys
> 
> Tino@TINONT ~
> $ chmod 644 .ssh/authorized_keys
> 
> Tino@TINONT ~
> $ logout
> Connection to tinont closed.
> 
> tino@tinux:~ > ssh tinont
> Last login: Sat Nov 16 18:12:51 2002 from tinux.tino-lange.de
> Fanfare!!!
> You are successfully logged in to this server!!!
> 
> Tino@TINONT ~
> $ ping tinux
> Fehler bei der Initialisierung der Windows-Socketsschnittstelle.
> Fehlercode 0.
> 
> Tino@TINONT ~
> $ rm .ssh/authorized_keys
> 
> Tino@TINONT ~
> $ logout
> Connection to tinont closed.
> 
> tino@tinux:~ > ssh tinont
> Last login: Sat Nov 16 18:12:51 2002 from tinux.tino-lange.de
> Fanfare!!!
> You are successfully logged in to this server!!!
> 
> Tino@TINONT ~
> $ ping tinux
> 
> Ping tinux [192.168.1.1] mit 32 Bytes Daten:
> 
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> Antwort von 192.168.1.1: Bytes=32 Zeit<10ms TTL=64
> 
> Ping-Statistik fr 192.168.1.1:
>     Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
> Ca. Zeitangaben in Millisek.:
>     Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms
> 
> Tino@TINONT ~
> $
> 
> Do you have an idea?
> Thanks!
> 
> Tino


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Corinna Vinschen]

On Wed, Nov 20, 2002 at 11:35:10AM +0100, Tino Lange wrote:
> Hi Cygwin-List!
> 
> Just discoverd that the same problem exists with ".ssh/authorized_keys2".
> 
> Can someone reproduce the problem?

No.  Btw., did you read http://cygwin.com/bugs.html?

And *additionally* what is the output of 

  getfacl $WINDIR/system32/wsock32.dll

and

  getfacl $WINDIR/system32/winsock.dll

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

Corinna Vinschen wrote:

Hi Corinna!

> No.  Btw., did you read http://cygwin.com/bugs.html?

You think my mail didn't contain enough information or wasn't formed well?

a) The subject line describes the problem very good
b) In the body there's a huge shell section captured, exactly showing 
the problem
c) I told you the relevant packages (latest version from the cygwin 
release)
d) the only multiple exclamation marks were from the sshd login itself 
in the quoted section...
e) I didn't assume that the bug is trivial
f) I didnt tell you personal stories - the mail was focused on the 
problem itself

The only point that is left is the cygcheck.out - did you mean that?

OK - why didn't I include a "cygcheck.out"?

a) maybe the information was already enough for you to locate the problem
b) "cygwin@cogwin.com" is a huge list - I don't want to spam lots of 
people with this information - if someone needs it I can send it to him 
personally I don't like to recieve lot's of cygcheck.out a day as a 
public reader of this list myself.
c) cygcheck.out can contain *lots* of personal information. I don't want 
Microsoft to spy on my computer why should I broadcast such information 
by myself actively on a mailinglist that's very huge, get's archived and 
so on?????

I have no Problem sending this file to you, Corinna, or some of your 
collegues - if you need such detailed information because all the other 
information was not enough. Just ask for it if you feel that you can 
maybe help and that you are the appropiate maintainer for my problem.

You just got it with separate mail.

> And *additionally* what is the output of 
> 
>   getfacl $WINDIR/system32/wsock32.dll
> 
> and
> 
>   getfacl $WINDIR/system32/winsock.dll

Of course - it's on its way.

Thanks and best regards

Tino



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

Corinna Vinschen wrote:

Hi Corinna!

> No.  Btw., did you read http://cygwin.com/bugs.html?

You think my mail didn't contain enough information or wasn't formed well?

a) The subject line describes the problem very good
b) In the body there's a huge shell section captured, exactly showing 
the problem
c) I told you the relevant packages (latest version from the cygwin 
release)
d) the only multiple exclamation marks were from the sshd login itself 
in the quoted section...
e) I didn't assume that the bug is trivial
f) I didnt tell you personal stories - the mail was focused on the 
problem itself

The only point that is left is the cygcheck.out - did you mean that?

OK - why didn't I include a "cygcheck.out"?

a) maybe the information was already enough for you to locate the problem
b) "cygwin@cogwin.com" is a huge list - I don't want to spam lots of 
people with this information - if someone needs it I can send it to him 
personally I don't like to recieve lot's of cygcheck.out a day as a 
public reader of this list myself.
c) cygcheck.out can contain *lots* of personal information. I don't want 
Microsoft to spy on my computer why should I broadcast such information 
by myself actively on a mailinglist that's very huge, get's archived and 
so on?????

I have no Problem sending this file to you, Corinna, or some of your 
collegues - if you need such detailed information because all the other 
information was not enough. Just ask for it if you feel that you can 
maybe help and that you are the appropiate maintainer for my problem.

You just got it with separate mail.

> And *additionally* what is the output of 
> 
>   getfacl $WINDIR/system32/wsock32.dll
> 
> and
> 
>   getfacl $WINDIR/system32/winsock.dll

Of course - it's on its way.

Thanks and best regards

Tino



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Corinna Vinschen]

On Wed, Nov 20, 2002 at 12:12:51PM +0100, Tino Lange wrote:
> The only point that is left is the cygcheck.out - did you mean that?

Yes.

> OK - why didn't I include a "cygcheck.out"?
> 
> a) maybe the information was already enough for you to locate the problem

No.

> b) "cygwin@cogwin.com" is a huge list - I don't want to spam lots of 
> people with this information - if someone needs it I can send it to him 
> personally I don't like to recieve lot's of cygcheck.out a day as a 
> public reader of this list myself.

It's one (better: the) purpose of the cygwin ML to send bug reports here
and to receive help if somebody actually knows a solution.

> c) cygcheck.out can contain *lots* of personal information. I don't want 
> Microsoft to spy on my computer why should I broadcast such information 
> by myself actively on a mailinglist that's very huge, get's archived and 
> so on?????

Then obfuscate stuff in the cygcheck output which you take for private.

> I have no Problem sending this file to you, Corinna, or some of your 

Perhaps, but *I* have problems with getting PM about Cygwin stuff.
Did you read the section "Shouldn't I just send email to straight to a
cygwin developer or package maintainer?", especially the "Reply-To:"
passage?

> You just got it with separate mail.

No, I didn't so far and I don't want to get PM further on.  This is the
reason I'm setting the Reply-To: to the ML and not using my real mail
address.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Christopher Faylor]

On Wed, Nov 20, 2002 at 12:51:29PM +0100, Corinna Vinschen wrote:
>No, I didn't so far and I don't want to get PM further on.  This is the
>reason I'm setting the Reply-To: to the ML and not using my real mail
>address.

This is all very confusing.  How about if I drop you a personal note to
discuss it?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Corinna Vinschen]

On Wed, Nov 20, 2002 at 11:49:02AM -0500, Chris Faylor wrote:
> On Wed, Nov 20, 2002 at 12:51:29PM +0100, Corinna Vinschen wrote:
> >No, I didn't so far and I don't want to get PM further on.  This is the
> >reason I'm setting the Reply-To: to the ML and not using my real mail
> >address.
> 
> This is all very confusing.  How about if I drop you a personal note to
> discuss it?
> 
> cgf

*kick*

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

Hi again, Corinna!

Hmmm, it seems we're more talking about other things than SSH - but it's
really quite interesting.
That's why I'd like to respond to your last mail from this afternoon.


> > a) maybe the information was already enough for you to locate the problem
> No.
OK. That's why you "asked" for the "cygcheck.out" -- in a very special
way :-)
And you recieved it immediately.
  

> > b) "cygwin@cogwin.com" is a huge list - I don't want to spam lots of
> > people with this information - if someone needs it I can send it to him
> > personally I don't like to recieve lot's of cygcheck.out a day as a
> > public reader of this list myself.

> It's one (better: the) purpose of the cygwin ML to send bug reports here
> and to receive help if somebody actually knows a solution.

Yes, that's also exactly what I think!

Bug reports. Bug descriptions. Questions. Sharing of knowledge. Of
course!
That's what mailing lists are for and that's why they are so efficient. 

Such a mailinglist is 
a) for finding together (the one who needs help with those who maybe can
help)
b) for discussing solutions/problems and so on
c) for *archiving* and searching for similar bugs or if maybe someone
else has the same problem - a kind of "database" to protect you as the
maintainers to answer the same questions twice or more

But that really doesn't mean that every message has to contain a huge
attachment with this detailed information which is send to *ALL*
maintainers and to *ALL* interested readers and archived forever in
*ALL* archives. The interesting part for the mailinglist is the part
besides cygcheck.out:
- a clear description of the problem, that is GOOGLE'able
- maybe: some interesting conversation
- a clear solution that summarizes and again is well GOGGLE'able



> > c) cygcheck.out can contain *lots* of personal information. I don't want
> > Microsoft to spy on my computer why should I broadcast such information
> > by myself actively on a mailinglist that's very huge, get's archived and
> > so on?????

> > I have no Problem sending this file to you, Corinna, or some of your
> Perhaps, but *I* have problems with getting PM about Cygwin stuff.
> Did you read the section "Shouldn't I just send email to straight to a
> cygwin developer or package maintainer?", especially the "Reply-To:"
> passage?

Of course I have read this part! And I agree!
I didn't propose to send *questions* to you or other maintainers
personally, or?
Maybe you misunderstood me? I didn't want "private" support - just you
and me. No!

I really like mailing lists - I only spoke about the "cygcheck.out"
Details which don't belong to the list in my opinion.

My understanding of the procedure was:

I ask on the mailinglist, to find someone who maybe can help.
The more detailed my question is the more chance I have to find someone,
of course...

If now someone like you says: "Hey, I saw the topic and the
description.  That's maybe something for me - I'll have a look at that,
please send me all those details from cycheck.out!" then we still *only*
use the mailinglist as basis and platform for communication - not
personal email-accounts - only exception is the cygcheck.out that should
be sent to the counterpart via a special email-account. Why sent these
25kByte to **thousands** of reciepients that are mostly not interested
in it (but maybe in the text-part of the mail)?

"cygwin@cygwin.com" has really *much* traffic. Thank god that not every
mail has a "cygcheck.out" attachement!
I think I would unsubscribe very fast as public reader although I like
to read the mail-bodys itself.



> > You just got it with separate mail.
> No, I didn't so far and I don't want to get PM further on.  This is the
> reason I'm setting the Reply-To: to the ML and not using my real mail
> address.

Meanwhile it should be there, or?
By the way: I bet "corinna-cygwin" is not you real PM, or? It's a
special cygwinlist email work-account and that's perfectly right.

Hope this clears up things a bit.
I really don't want to change some common behaviour here but on the
other hand I don't think it's right to ignore me / my questions  - or to
just treat me with your "have you read our FAQ" if I just deliver the
cygcheck.out differently. 

Best regards again

Tino

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Max Bowsher]

Tino Lange <Tino.Lange@isg.de> wrote:

> I really like mailing lists - I only spoke about the "cygcheck.out"
> Details which don't belong to the list in my opinion.

cygcheck output is a vital tool in diagnosing problems.... therefore:

> I didn't propose to send *questions* to you or other maintainers
> personally, or?
> Maybe you misunderstood me? I didn't want "private" support - just you
> and me. No!

by giving the most effective tool to diagnosing problems only to Corinna,
you were saying "I only trust Corinna to help me" - i.e. you were asking for
private support.

When asked, post cygcheck output publicly. Sanitize it first if you feel the
need, but I've just looked through a cygcheck on my machine, and found
nothing I was worried about disclosing to the list.

> My understanding of the procedure was:
>
> I ask on the mailinglist, to find someone who maybe can help.
> The more detailed my question is the more chance I have to find
> someone, of course...
>
> If now someone like you says: "Hey, I saw the topic and the
> description.  That's maybe something for me - I'll have a look at
> that, please send me all those details from cycheck.out!" then we
> still *only* use the mailinglist as basis and platform for
> communication - not personal email-accounts - only exception is the
> cygcheck.out that should be sent to the counterpart via a special
> email-account.

No. The cygcheck.out is part of the info that should be sent in the first
place.

> Why sent these 25kByte to **thousands** of reciepients
> that are mostly not interested in it.

More like 15kB. Insignificant compared to the volume of the list.

> (but maybe in the text-part of the mail)?

Don't do this. It clutters the archives.

> "cygwin@cygwin.com" has really *much* traffic. Thank god that not
> every mail has a "cygcheck.out" attachement!

Every mail won't. Only the ones asking for help on a problem they haven't
been able to localize.

> By the way: I bet "corinna-cygwin" is not you real PM, or? It's a
> special cygwinlist email work-account and that's perfectly right.

If someone says "Do not send me personal mail", it means "Do not send me
personal mail", not "Look at my email address and decide you want to send me
personalized email anyway".

> Hope this clears up things a bit.
> I really don't want to change some common behaviour here but on the
> other hand I don't think it's right to ignore me / my questions

Well, if you go against both mailing list policy, and stated personal
opinions, then you should expect to be ignored.

--
Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Christopher Faylor]

Max Bowsher has already answered all of this very well, but I need to
make a few additional points.

On Thu, Nov 21, 2002 at 01:57:54AM +0100, Tino Lange wrote:
>>>I have no Problem sending this file to you, Corinna, or some of your
>>
>>Perhaps, but *I* have problems with getting PM about Cygwin stuff.  Did
>>you read the section "Shouldn't I just send email to straight to a
>>cygwin developer or package maintainer?", especially the "Reply-To:"
>>passage?
>
>Of course I have read this part! And I agree! I didn't propose to send
>*questions* to you or other maintainers personally, or?  Maybe you
>misunderstood me?  I didn't want "private" support - just you and me.
>No!

It is obviously you who are misunderstanding.  The words at the
indicated web page don't make *any* allowances for sending personal
email and they are pretty clear that the cygcheck output is supposed to
be included "in your report".  You really don't have any basis
for assuming that personal email is the way to go.

>I really like mailing lists - I only spoke about the "cygcheck.out"
>Details which don't belong to the list in my opinion.

Your opinion is wrong for this list and for most of the project mailing
lists on the internet.

>"cygwin@cygwin.com" has really *much* traffic. Thank god that not every
>mail has a "cygcheck.out" attachement!

No one suggested that every email should have a cygcheck.out attachment.
http://www.nizkor.org/features/fallacies/straw-man.html

>>>You just got it with separate mail.
>>No, I didn't so far and I don't want to get PM further on.  This is the
>>reason I'm setting the Reply-To: to the ML and not using my real mail
>>address.
>
>Meanwhile it should be there, or?  By the way: I bet "corinna-cygwin"
>is not you real PM, or?  It's a special cygwinlist email work-account
>and that's perfectly right.

It's actually a special "bounce this clueless email back to the sender"
account.  You should have received a bounce indicating that it did not
go through, in fact.

>Hope this clears up things a bit.

Max said it well:

*>Well, if you go against both mailing list policy, and stated personal
*>opinions, then you should expect to be ignored.

cgf
--
Please do not send me personal email with cygwin questions or observations.
Use the resources at http://cygwin.com/ .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

[-- Attachment #1: Type: text/plain, Size: 2975 bytes --]

Corinna, Max, Christopher,

hallo again. Thanks for your answers!

I still see things a bit different, but anyhow - I have to accept your 
rules. It's your list - you make the rules - the user wishing to have 
help has to follow of course... And that's OK and fair.




> by giving the most effective tool to diagnosing problems only to Corinna,
> you were saying "I only trust Corinna to help me" - i.e. you were asking for
> private support.

I also would have sent it to you and/or other people asking for it. I 
just didn't want to broadcast it to *thousands* that - for sure - won't 
look into it but are "forced" to recieve it.

OK, maybe that's some personal problem. I also still don't like 
HTML-Mails or these useless VCards in E-Mails too. Also I don't like 
emails with much more quoted text than the newly written part. I always 
try to keep attention on the resource "bandwidth" and "size" if my mails 
can reach lots of people that didn't ask for my mails - like it's the 
case in mailinglists




> When asked, post cygcheck output publicly.

Yep. I just thought first that this was a real good compromise.

Looking back in the history I find that most of the questions could be 
answered without "cygcheck.out" as the *very first information*. So the 
user asking for help can send it to the list after the first "contact", 
on request of someone how felt that it's needed for the solution.

But: Corinna, you did not ask. My mail was ignored until I gave some 
additional information - then it was no "please send the cygcheck.out" - 
it was a "didn't you read our FAQ". So you expected "cygcheck.out" in 
the *first* mail.

But anyhow, that's cleared now. Thanks for your mails - for not ignoring 
again, but discussing. At least for me it was really interesting.

I understand/accept now that everyone subscribing to the list has to 
know the regulations and should be prepared for not only discussion and 
bug reports but also for "cygchecks.out" and other attached stuff.





 >Sanitize it first if you feel the
 >need, but I've just looked through a cygcheck on my machine, and found
 >nothing I was worried about disclosing to the list.

That depends on the configuration and the environment :-)

Maybe you should add that in your "http://cygwin.com/bugs.html": one is 
allowed to sanitize the file and one should maybe compress it before 
sending.

It's really fair that all those files you wish to recieve are plain 
ascii so it's human readable and understandable what information is sent.



---------------------------------------------------------------------

OK. Back to buisiness, let's stop the off-topic thread :-)

I hope my information in the first mail about my sshd problem was enough 
- especially now that it's completed by my cygcheck.out and the two 
additional files you requested. Maybe you can help me finding the problem?

If there's still some information missing or incomplete just let me know.

Best regards again

Tino





[-- Attachment #2: debug_logs_tlange.zip --]
[-- Type: application/x-zip-compressed, Size: 5113 bytes --]

[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Christopher Faylor]

On Thu, Nov 21, 2002 at 09:12:32AM +0100, Tino Lange wrote:
>>Sanitize it first if you feel the need, but I've just looked through a
>>cygcheck on my machine, and found nothing I was worried about
>>disclosing to the list.
>
>That depends on the configuration and the environment :-)
>
>Maybe you should add that in your "http://cygwin.com/bugs.html": one is
>allowed to sanitize the file and one should maybe compress it before
>sending.

Of course you can sanitize it and it should *not* be compressed.  The
intent is to look at the output as easily as possible.

cgf
--
Please do not send me personal email with cygwin questions or observations.
Use the resources at http://cygwin.com/ .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

>> [ "cygcheck.out" ]
> Of course you can sanitize it and it should *not* be compressed.  The
> intent is to look at the output as easily as possible.

Hi Christopher,

Ooops - now I have sent it compressed (zip) this morning - again in my
intent to save space and resources...
But OK - shall I send it again to the list, this time uncompressed? Or
will you and your collegues make just another exception for me? 

Cheers,

Tino

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: SSHD: error initializing windows sockets if I use ".ssh/authorized_keys"

[Tino Lange]

Tino Lange wrote:

Hi!

If maybe someone looks at this problem in the next time - I'm on holiday 
for 3 1/2 weeks. So don't wonder if I don't reply...

So I'm not impolite - just not there :-)

Have a nice time!
Cheers

Tino



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/