All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: User-level Tasks in Hotplug Scripts?
Date: Tue, 05 Feb 2002 15:05:36 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101292153517698@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101256895903801@msgid-missing>

i didn't realize this was such a hot topic!

On Mon, 4 Feb 2002 11:28:51 -0800 (PST)
Jim Carter <jimc@math.ucla.edu> wrote:

> On Fri, 1 Feb 2002, Ryan Shaw wrote:
>
> > Hotplugging scripts are run as root, so I have
> > the following line to launch nautilus: [which won't start]
> >
> > su - ryan -c "nautilus --display=:0.0 > /home/ryan/nautilus.log 2>&1" &
> 
> In your case, I'd suggest doing an imitation of xdm -- copy the auth file
> to a file in /tmp owned by you and mode 600, and XAUTHORITY=/tmp/thatfile.
> Then do the "su".  Then if your kid in middle school is using your machine,
> he/she can plug in the camera and see the pics, but can't do much damage
> through the X authorization.  (And, since the kid is the console user, the
> auth file properly belongs to him, so essentially you've stolen it from
> him, not him from you.)

i tried this--no dice. but i'm starting to think that this
is specifically a nautilus problem. just doing 

su - ryan -c "$PROGRAM --display=:0.0"

in the hotplug script (without setting XAUTHORITY) works for 
about everything i've tried, including gnome apps, but not 
for nautilus. unfortunately, nautilus is not printing anything 
to stdout or stderr, so i can't figure out what it is missing, 
and no one on the nautilus-dev list seems to know either.

anyway, thanks for the suggestions. i'm interested to see
what comes out of the discussion i unintentionally sparked.

ryan

 

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2002-02-05 15:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 13:09 User-level Tasks in Hotplug Scripts? Ryan Shaw
2002-02-01 23:58 ` David Brownell
2002-02-02 20:55 ` Jim Gettys
2002-02-02 22:02 ` Oliver Neukum
2002-02-02 22:12 ` Jim Gettys
2002-02-02 22:52 ` Oliver Neukum
2002-02-02 23:02 ` David Brownell
2002-02-03  0:58 ` Scott Cuyle Fritzinger
2002-02-03  8:36 ` Greg KH
2002-02-04  6:02 ` Dmitry Yu. Bolkhovityanov
2002-02-04 15:10 ` Jim Gettys
2002-02-04 19:28 ` Jim Carter
2002-02-05  3:32 ` David Brownell
2002-02-05 15:05 ` Ryan Shaw [this message]
2002-02-06 14:30 ` Marcus Harnisch
2002-02-06 14:54 ` Jim Gettys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-101292153517698@msgid-missing \
    --to=ryan.shaw@stanfordalumni.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.