Comet As Service


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Jon Sacks on August 01, 2006 at 11:24:22: Uploaded files: 1

A few issues…

1. In the Comet As Service setup there is a field for “Additional Command Line Parameters”. I tried to use this so it would fire up a session using the /keyfile parameter. Nothing happens.

2. Comet As Service does not handle "N" type directories as the client does and starting Comet As Service then starting the client seems to negate the ability of the client to attach to the "N" type directory. This is important, we have some one way directories (i.e. FTP server directories) that we trade files through. Is there a work around? Is this a bug or a feature?

3. I started Comet As Service and it is sitting in the tray idle, right click on it and an option is there to “Start Comet as Service”, I click on Start and get the attached error.

This can be a very powerful addition, the ability to start the Comet Anywhere host is obvious and I want to be able to run the XAP server the same way, the problem on the XAP side is XAPMON must be running, how can I start the service and have XAPMON fired up (hence the /keyfile I tried)?

JSACKS<<



Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]