Hello, everyone:
Recently I installed ver 2.2 of debian on a new machine for netsaint
monitoring. Previously, I had experience only with Redhat distros.
Everything was going ok until i decided to give webmin
(http://www.webmin.com) a try. It installed ok, but when I created the
group netsaint
Jason Willoughby hat gesagt: // Jason Willoughby wrote:
> On Sun, 6 Jun 1999, Alisdair McDiarmid wrote:
>
> > [root%letdown /home/alisdair] # xmcd
> > Xlib: connection to ":0.0" refused by server
> > Xlib: Client is not authorized to connect to Server
> > Error: Can't open display: :0.0
>
> Yeah
On Sun, Jun 06, 1999 at 12:29:58AM +, Alisdair McDiarmid wrote:
> I've got problems running X apps as root with xdm.
See /usr/doc/xfree86-common/FAQ.
--
G. Branden Robinson | Measure with micrometer,
Debian GNU/Linux | mark with chalk,
[EMAIL
On Sat, Jun 05, 1999 at 07:58:36PM -0400, Jason Willoughby wrote:
>
> Yeah, xdm is more paranoid than startx. You can disable access controls
> by running, as alisdair, "xhost +". Check the man page for more info.
great, thanks!
--
alisdair mcdiarmid
[i won't tear again i won't breathe in the
On Sun, 6 Jun 1999, Alisdair McDiarmid wrote:
> [root%letdown /home/alisdair] # xmcd
> Xlib: connection to ":0.0" refused by server
> Xlib: Client is not authorized to connect to Server
> Error: Can't open display: :0.0
Yeah, xdm is more paranoid than startx. You can disable access controls
by r
I've got problems running X apps as root with xdm.
If I log in as alisdair (my main user) and su root in a terminal
window, any attempt to run an X application fails:
[root%letdown /home/alisdair] # xmcd
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Ser
On 03-Jun-99 Chris wrote:
> On Thu, Jun 03, 1999 at 05:14:22AM -, Pollywog wrote:
>>
>> On 03-Jun-99 Chris wrote:
>> > It looks like some element relating to su has been broken. I apologize
>> > for
>>
>> Yes, it is shellutils package, and to fix it, just make /bin/su suid root.
>>
> Yep,
On Thu, Jun 03, 1999 at 05:14:22AM -, Pollywog wrote:
>
> On 03-Jun-99 Chris wrote:
> > It looks like some element relating to su has been broken. I apologize for
>
> Yes, it is shellutils package, and to fix it, just make /bin/su suid root.
>
Yep, that did the trick. Thanks! Now, my next
On Thu, 3 Jun 1999, Chris wrote:
> It looks like some element relating to su has been broken. I apologize for
> not knowing which package contains su, but I have the latest version for
> Potato (x86) as of Wednesday (yesterday). I've just discovered that
> su fails to work on the console, too.
On 03-Jun-99 Chris wrote:
> It looks like some element relating to su has been broken. I apologize for
> not knowing which package contains su, but I have the latest version for
> Potato (x86) as of Wednesday (yesterday). I've just discovered that
> su fails to work on the console, too. Should
Well, living on the blleding edge seems to have finally bitten me in the ass
;-) I normally do an apt-get update;apt-get upgrade every week or so unless
I hear about major fixes. I did such an upgrade earlier today, upgrading
nearly everything that could be upgraded. The only immediate abnormali
All of the suggestions were more or less appropriate, but I think a
more secure way to grant another user the right to run programs on
your display is to use xauth. See the xauth manpage for more details,
but I use
xauth extract - $DISPLAY | rsh otherhost xauth merge -
to allow *only* myself
I just tried a couple of thing that seem to work.
1. Put the "export XAUTHORITY=~paul/.Xauthority in your
.bashrc file. When you su to another user the XAUTHORITY
environment variable still exists! Works fine.
2. Did you ever notice what happens when you su to another
user with the USER
I just do:
8<->8
~ # pwd
/root
~ # ln -s /home/karlheg/.Xauthority .
8<->8
I've also got "~karlheg/.emacs" and several other files like it
symlinked in the same way for
On Jun 2, Ed Donovan wrote
>
> You could just add
>
> xhost +localhost
>
> to your .xinitrc file, if you don't have any xhost commands there
> already. Jens has suggested "export XAUTHORITY=~paul/.Xauthority"; I
> don't immediately know which method would be preferable. The xhost
> method wo
> "Paul" == Paul McDermott <[EMAIL PROTECTED]> writes:
Paul> Hi folks, I just installed X version 3.2 on my system this
Paul> past few weeks. I am having problems do things as su. ie for
Paul> the first error message is one that I receive whenever I try
Paul> to run an X progr
thanks jens, is there a way so i don't have to type the command all the time?
thanks again.
Paul
On Mon, 2 Jun 1997, Jens B. Jorgensen wrote:
> Paul McDermott wrote:
> >
> > Hi folks, I just installed X version 3.2 on my system this past few
> > weeks. I am having problems do things as su. ie
Before you "SU" to root type 'xhost +' this will disable X windows access
control. Remember X windows is a network program and has to authorize
every user before it will let you run an application.
By the way xhost + is also not the most secure way of handling this
problem. Do a 'man xhost' an
Paul McDermott wrote:
>
> Hi folks, I just installed X version 3.2 on my system this past few
> weeks. I am having problems do things as su. ie for the first error
> message is one that I receive whenever I try to run an X program as su.
> This error message is when I was trying to use xclock. I
Hi Roberto, I did use su. I can't run any x programs as su, only as user
paul. Any other ideas.
On Mon, 2 Jun 1997, Roberto Magana wrote:
> Use su -
>
> %
>
> <[EMAIL PROTECTED]> Roberto Magana. Escuela de Fisica UCR.
>
Use su -
%
<[EMAIL PROTECTED]> Roberto Magana. Escuela de Fisica UCR.
(The Physics Dept. University of Costa Rica.)
%
--
TO U
Hi folks, I just installed X version 3.2 on my system this past few
weeks. I am having problems do things as su. ie for the first error
message is one that I receive whenever I try to run an X program as su.
This error message is when I was trying to use xclock. I have check
xclocks permissi
22 matches
Mail list logo
