Was there anything in particular you are referring to in the README,
or is this a general RTFM comment? I have read the READMEs, googled the
list for 5 days, picked apart the install scripts, tested with
alternative services, reinstalled, etc. I would like to think that I've
done my home
Hi Mark,
Thanks for you reply.
Regarding #1, yes the last 2 lines of the cygrunsrv command were joined
on my terminal (the email client must have wrapped them).
On #2, what the heck? :) I'm not saying that you are wrong about the
behaivor, but the shell ought to have striped the quotes
Mike Dunn wrote:
Larry Hall (Cygwin) wrote:
On 05/06/2006, Mike Dunn wrote:
I did just test by running cron from the command line (not as a
service), and it appears to work fine. I suspect, that it can only
exec commands under my uid, since my account does not have things
like
[EMAIL PROTECTED] ~
$ cygrunsrv -I sshd --shutdown -p /usr/sbin/sshd -a -D -ddd \
-d CYGWIN sshd -u sshd_server -w a_fine_password -e
CYGWIN=binmode ntsec tty
1. I assume that you meant to provide a \ after '-e' in the
second line of your command above, correct?
2. In my earlier
Indeed I did run it. Cron_diagnose complained about permissions that I
fixed by chowning the files/directories to the Administrators group.
But those changes did not change cron's behaivor.
I did just test by running cron from the command line (not as a
service), and it appears to work
On 05/06/2006, Mike Dunn wrote:
I did just test by running cron from the command line (not as a service),
and it appears to work fine. I suspect, that it can only exec commands
under my uid, since my account does not have things like
SeCreateTokenPrivilege, etc.
Right. And by running it
Good question ;). I have not been able to find one, but I don't
necessarily know where to look (i'm not much of a windows guy).
I'll keep looking, but cron is showing the same behaivor as sshd, and cron
AFAIK does not bind to a tcp port. I had ruled out a firewall due to
cron's behaivor.
Thanks
Mike Dunn wrote:
Good question ;). I have not been able to find one, but I don't
necessarily know where to look (i'm not much of a windows guy).
I'll keep looking, but cron is showing the same behaivor as sshd, and cron
AFAIK does not bind to a tcp port. I had ruled out a firewall due to
I've been having problems getting cron/sshd to work properly (as
services or not as services) on a Win 2003 server. I understand that
certain attributes of the SYSTEM account changed in win2003, and I've
tried to allow ssh-host-config to setup sshd, but with no success. I
have tried
# If there is a running service, then stop it and remove it.
cygrunsrv --query sshd /dev/null 21 {
cygrunsrv --stop $service;
cygrunsrv --remove $service;
};
Correction: '$service' should be replaced with 'sshd' in the two
lines above.
--
Unsubscribe info:
Hi Mark,
Thanks for looking at this with me. I have restarted the sshd service
many times, and have provided the password for the sshd_server account
each time I've installed the service (whether installing it manually or
with ssh-host-config). Below is how I have been typically installing
Mike Dunn wrote:
[snip]
It's strange how the service starts normally, and sshd enters the
process table, but it appears to refuse to run. I wonder if there is a
way to test my password for the sshd_server account (or would cygrunsrv
complain if it were wrong?)
Do you have a firewall running
12 matches
Mail list logo
