[CLUG] linuxconf over X

[Collins_Paul at emc.com]

does a backtrace from the core dump reveal anything obvious?

> -----Original Message-----
> From: Peter Flynn [mailto:pflynn at imbolc.ucc.ie]
> Sent: 10 February 2000 09:48
> To: cork at linux.ie
> Subject: [CLUG] linuxconf over X
> 
> 
> Why won't linuxconf -display foo.bar.ie:0.0 & work?
> 
> The user is logged into an RH5.2 box from a PC, running
> Reflection X, which we have used successfully for remote
> management many times running against Suns and Alphas.
> 
> xhost is therefore presumably set correctly, and the
> use is logged inwith a userid whose privs are set to 
> allow use of linuxconf and to become superuser.
> 
> $ linuxconf -display foo.bar.ie:0.0 &
> [1] 21319
> $ <user hits CR>
> [1]    Segmentation fault     linuxconf -display 
> foo.bar.ie:0.0 (core dumped)
> $ su
> Password: 
> # linuxconf -display foo.bar.ie:0.0 &
> [1] 21641
> # <user hits CR>
> ** ERROR **: sigsegv caught
> remadmin (GUI frontend) exiting abnormaly
> 
> [1]+  Exit 255                linuxconf -display foo.bar.ie:0.0
> #
> 
> Is linuxconf crocked, or is there some additional layer
> of protection going on here? This is going to kill Linux
> as a server OS here if this doesn't work.
> 
> ///Peter
> 
> _______________________________________________
> Cork maillist  -  Cork at linux.ie
> http://www.linux.ie/mailman/listinfo/cork
>