Corinna Vinschen writes: > It doesn't matter if it's the same. An exception is generated and 32 > and 64 bit versions react differently for whatever reason. It's also > really unnecessary to generate two accounts for this.
I know that now. But at one point I was wondering if somehow the fact that certain settings in the cyg_server user account point to the 64bit installation was responsible for my problem as it looked like there was some interaction. > Setting up sshd should be the job of an admin in the first place. The > domain account is a service starter account, not just some arbitrary > administrative account. That, and much easier maintainance domain-wide > should be blatantly obvious to the admins. I am the admin, but just of that single server and not all the time. As I said I can and will ask, but even if the guy I'm talking to agrees it makes sense that still doesn't mean it's going to happen once it's been filtered through their set of rules that don't have provisions for Cygwin in them. They've already asked why I don't convert that box to Linux (different rules again which at least know of sshd) and I actually might end up having to do so in the long run. > Thanks, coming... Appreciated. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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
