The following is from
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
This is the trouble I am having.
"Btw., when running on 2K3, the SYSTEM user has not enough privileges to
switch the user context w/o password, which will spoil using rsh a
bit... See the /bin/sshd-host-config script from the openssh package,
which installs not only the sshd serice, but also creates a new user
account called "sshd_server", which has the necessary privileges to do
that. You could remove the inetd service and recreate it again after
running /bin/sshd-host-config like this:
cygrunsrv -R inetd
cygrunsrv -I inetd -u sshd_server -w <sshd_server's password> ..."
> -----Original Message-----
> From: owner-amanda-users AT amanda DOT org [mailto:owner-amanda-users AT
> amanda DOT org]
> On Behalf Of rom
> Sent: Friday, July 14, 2006 4:12 PM
> To: amanda-users AT amanda DOT org
> Subject: Re: bygwin amanda client behind firewall.
>
>
> McGraw, Robert P. wrote:
> > Well I am getting a little closer.
> >
> > My cygwin client is a Window2003 server.
> So is mine.
>
> >
> > When I do a amcheck from the amanda server to the cygwin client behind
> the
> > firewall I now get the following in the events log on the cygwin client.
> >
> > "....The following information is part of the event: inetd: PID 2280:
> > amanda: can't set uid 18: Permission denied.....
> >
> > "...The following information is part of the event: inetd: PID 2764:
> > /local/Amanda/amanda-2.4.5p1/libexec/amandad: exit status 0x100."
> >
> > So now I am at least getting to the inetd service.
> >
> > The following are some things that I have done to tray an track down why
> > amanda can't set uid 18:
> Documentation says that you should use tab and not spaces to separate
> the tokens on inetd.conf. I don't know if that is really an issue but
> it's always better to remember.
>
> And you can check which user inetd is running as. To find that, dclick
> the taskbar, Task manager, go to the Processes tab, select the Show all
> users processes checkbox, find inetd and check which user it's running as.
>
> It should be running as SYSTEM. If it's not, that could be the problem.
>
> I would add that I was running as user Administrator of the local
> machine (not administrator of the domain) when I ran inetd with
> --install-as-service.
>
> Bye!
>
> Robert
[McGraw, Robert P.]
The following is from
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
This is the trouble I am having.
"Btw., when running on 2K3, the SYSTEM user has not enough privileges to
switch the user context w/o password, which will spoil using rsh a
bit... See the /bin/sshd-host-config script from the openssh package,
which installs not only the sshd serice, but also creates a new user
account called "sshd_server", which has the necessary privileges to do
that. You could remove the inetd service and recreate it again after
running /bin/sshd-host-config like this:
cygrunsrv -R inetd
cygrunsrv -I inetd -u sshd_server -w <sshd_server's password> ..."
Does this ring a bell.
Robert
smime.p7s
Description: S/MIME cryptographic signature
|
