Re: [cobalt-developers] connecting to cced remotely

[Derek Belrose <derek@xxxxxxxxxxxxx>]

Thank you for all of your help.  I will ask if I have anymore questions.

Derek

On Saturday 18 January 2003 06:41 pm, Rick Combest wrote:
> The control station protocol is proprietary.
>
> You are going to have to execute a cce session on each RAQ you wish to
> configure.  Your programming choices are C, Perl or PHP.
>
> I would be very careful how you interface with cce as it is equivalent to a
> root shell.
>
> Rick
>
> -----Original Message-----
> From: cobalt-developers-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx]On Behalf Of Derek Belrose
> Sent: Saturday, January 11, 2003 3:26 PM
> To: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-developers] connecting to cced remotely
>
> so it installs an application that listens on each server?  Or is this
> already
> available on the default unit before it is "owned" by the SCCS?
>
> On Saturday 11 January 2003 06:18 pm, Bruce Timberlake wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > > The reason I ask is because this isn't a perl application.  It's
> > > actually a client application that is going to be written in Java
> > > that will allow certain aspects of CCE to be changed, like user
> > > information, etc.
> > >
> > > The raq3 and raq4 was simple as that was just a SQL query, but this
> > > is somewhat more complex.  Access to a direct socket would have
> > > been ideal.  How does the Control Station do this?  Does it connect
> > > to a socket?  Or does it open up a shell remotely and run CCE?
> >
> > Control Station talks, via encrypted info, to an agent listening on
> > port 27000 on each remote appliance that the Control Station
> > 'owns'...
> >
> > - --
> > Bruce Timberlake
> > 
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.1 (GNU/Linux)
> >
> > iD8DBQE+IKYovLA2hUZ9kgwRAgC8AJ4qML4M6kPt/Tmf0b117T7p/qEn4ACfaLKk
> > 1oXlSqV9VAlYQ7Xv0oda0Bw=
> > =zRgH
> > -----END PGP SIGNATURE-----
> >
> > _______________________________________________
> > cobalt-developers mailing list
> > cobalt-developers@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-developers
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers