I would think running it in the background with nohup would be a good idea
....
as then u'd get loads of information on whatzz happening on the console!!
----- Original Message -----
From: "John D. McDonald" <[EMAIL PROTECTED]>
To: "jboss list" <[EMAIL PROTECTED]>
Sent: Saturday, November 04, 2000 7:51 PM
Subject: [jBoss-User] Starting jboss as a job on Solaris
> -All
> We are putting jboss into production next week(the 11th)! We decided to
use
> the "at" command to schedule a job to start jboss on the solaris box. With
a
> "regular" job that runs, and completes, in a reasonable amount of time,
the
> at command seems fine. However, with jboss, which will run for an
indefinite
> amount of time, are there any known side effects to "at" with processes
that
> run... for a long time. Also is there a better way to start jboss on
> Solaris?
>
> Thanks.
>
> -john
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
