"Jesus M. Salvo Jr." wrote:
> I believe the above is NOT possible, because of the requirement for X,
> but just to be sure...
>
> I don't have a problem running a Java Swing-less and AWT-less program at
> boot time, ... but is there a way to have a Java Swing program,
> therefore requiring X, to startup at boot time? ... and when the user (
> the user that was 'su -' during startup to run the Java Swing program )
> logs-in on X , he/she can see and interact with that Swing program that
> was started at boot?
The AWT classes (also used by Swing) need to find the X display when
they're first loaded. If X isn't running, the Java client fails. If X is
running but not receptive to client connections (such as during the
XDM login screen), the client may fail and/or hang. About the best you can
do is implement a try/timeout/sleep/retry loop - it might work to do it in
your program, or you may need to do that within some script that launches
your program.
Nathan
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
