🚀 go-pugleaf

Grahame M. Kelly - Linux User (gmkelly@zip.com.au) wrote:
: ...

: I have tried to get the xterm to automatically run at startx time by:
: "xterm -geometry 69x2+581+711 -e telnet localhost UPSstats -T UPSstats &"
: without success in my .xinitrc session. File permissions etc are OK.
: And I preferr the fvwm, but this should not make any difference I would
: have thought.

	How is it failing? Are there any error messages. It's kind of hard
to help without this sort of information.

: Also I can't see (in the man pages) how to let the Xserver know I want
: to run this window as Sticky.

	Stickyness is up to the window manager, not the X server.

	You may be better off starting the program from your fvwmrc, rather
than from .xinitrc. I think fvwm2 at least can specify certain types of
window as always sticky. Don't know about fvwm though.

--
David Gibson @ The Lorax	| New from Microsoft...
david%brucehall20@anu.edu.au	| 	THNEED 95
				| Which everyone, Everyone, EVERYONE needs.

Hi David,

>: I have tried to get the xterm to automatically run at startx time by:
>: "xterm -geometry 69x2+581+711 -e telnet localhost UPSstats -T UPSstats &"
>: without success in my .xinitrc session. File permissions etc are OK.
>: And I preferr the fvwm, but this should not make any difference I would
>: have thought.
>
>	How is it failing? Are there any error messages. It's kind of hard
>to help without this sort of information.
>


If I execute within a xterm the "telnet localhost UPSstats ...etc" then the
correct output is displayed. If I do a "xterm -geo... -e telent local...etc"
then I get "xterm: fatal IO error 2 (Broken Pipe) or KillClient on Xserver 0:0"
It appears as though the "xterm -e" directive does not work correctly or 
because of the way I have it set up. This happens also whilst within fvwm2
xterm so the problem is confined to how I do the "xterm -e".

Running it automatically via .xinitrc would be the next step once I was
able to get it to work correctly from within a xterm.



>: Also I can't see (in the man pages) how to let the Xserver know I want
>: to run this window as Sticky.
>
>	Stickyness is up to the window manager, not the X server.
>
>	You may be better off starting the program from your fvwmrc, rather
>than from .xinitrc. I think fvwm2 at least can specify certain types of
>window as always sticky. Don't know about fvwm though.

My mistake, make that fvwm2 not fvwm. Same question though.

Thanks Grahame

In article <pu9nk5.6s.ln@bushrock.zip.com.au>,
Grahame M. Kelly - Linux User <gmkelly@zip.com.au> wrote:
>Hi All,
>
>I have a UPS monitor program that I can run from a X terminal screen by
>"telent localhost UPSstats" which then every second or so puts the
>UPS status line " Mains 240VAC, Battery 99% etc...".
>
>What I wish to do is have a xterm run at a given position on my 
>virtual X screen that runs the telnet session automatically at startup
>and in Sticky mode.
>
>I have tried to get the xterm to automatically run at startx time by:
>"xterm -geometry 69x2+581+711 -e telnet localhost UPSstats -T UPSstats &"
>without success in my .xinitrc session. File permissions etc are OK.
>And I preferr the fvwm, but this should not make any difference I would
>have thought.

The '-e' parameter should be the last on the xterm command line:

xterm -geometry 69x2+581+711 -T UPSstats -e telnet localhost UPSstats &

>Also I can't see (in the man pages) how to let the Xserver know I want
>to run this window as Sticky.
>
>Could anyone help me ? 

Give the xterm instance a unique name (UPSstats) with the command line
option '-name' (this will also set the title name so with this you
dont need the '-T' option)  and then in your .fvwm(2)rc make an appropriate
'Style' line.

Style "UPSstats" Sticky



-- 
Ben Buxton_____________________    o    _          _--_|\   ZIP Internet P/L
Zip Guy   bb@zip.com.au       /____|___|_)________/______\______________________
Voice:   9270-4777                     | .        \_.--._*    Virtually
Dial-in: 9247-7288, 9247-9144    Fax: 92475276          v     the best :)

On Wed, 7 May 1997 09:28:14 +1000, Grahame M. Kelly - Linux User <gmkelly@zip.com.au> wrote:
>It appears as though the "xterm -e" directive does not work correctly or 
>because of the way I have it set up. This happens also whilst within fvwm2
>xterm so the problem is confined to how I do the "xterm -e".


        Exec    "Postbox"     exec /usr/bin/X11/xterm -sb -sl 500 -j -ls  -title
 Postbox -N Postbox -e ssh postbox -l root &



That works for me, inside .fvwmrc

(as a menu item)

Zebee