From: Mike Civil on
In article <45dcb47b.0(a)entanet>, Simon Waters <a(a)technocool.net> wrote:
>echo "export ICEAUTHORITY=/tmp/.ICEauthority" >>$HOME/.gnomerc

OK as long as only one user ever starts an X session?

Mike
From: Nix on
On 21 Feb 2007, Simon Waters outgrape:

>> On 16 Feb 2007, Simon Waters told this:
>>
>>> This is to allow mounting of $HOME over sshfs (I said it was a bad reason).
>>
>> Well, that's an interestingly weird thing to try :)
>
> I need a good network file system, and I'm just pissed at having to rebuild my
> kernel yet again, because I didn't include the kernel support for NFS, the

Er, why not preserve your .config? I keep mine in a quilt patch series along
with every other kernel hack I make, and I've never lost it. (I've occasionally
built a kernel with the entirely-default config, but that's soon detectable
when it utterly fails to boot :) )

> I suspect sshfs won't be up to the job either, but at least I don't have to hack
> around to make it secure, or rebuild any kernels. I'm having enough trouble
> setting an environment variable - so probably best I don't try anything
> more complicated than setting environment variables.

You might want to have a look at <http://fs.net/> as well. It's sadly
unmaintained but a really nifty idea.

> So far I've mostly used sshfs, to run the wrong version of subversion client,
> against my working copy of projects?! Don't do that.

Er, oops? (mind you, svn should warn you, unless you ran a too-*new* version
and it updated your working copy's version on you :) )

>> I suspect that you're simply not managing to instruct gdm to set the
>> environment variable for its children properly: try looking in
>> /proc/[gnome-session's PID]/environ to be sure.
>
> I need you at work to point out the more blindingly obvious things I fail to do
> there as well.

Well, I'm in the jobs market after a fifth year running with no pay
rise... :)

--
`In the future, company names will be a 32-character hex string.'
--- Bruce Schneier on the shortage of company names
From: Nix on
On 21 Feb 2007, Simon Waters verbalised:

>> It's called by gnome-session/ice.c, which calls IceAuthFileName()
>> appropriately and so should respect $ICEAUTHORITY.
>
> Knowing it is gnome-session that writes it got me sorted.
>
> I should "use the source" more ;)

The problem then is that I get lost without it: Oracle's buggered up
again, Solaris 8's gone wrong again, what's wrong? Search me...

> So the answer (Debian Sid & GNOME specific perhaps) was;
>
> echo "export ICEAUTHORITY=/tmp/.ICEauthority" >>$HOME/.gnomerc

Great! :)

> I guess I should have "known" that much about GNOME by now,

I think this is Debian-specific anyway.

> but I've never needed a GNOME specific environment variable

All the *dm's have their own weird independent way of setting this sort
of thing. (It's one of many reasons why I still use startx / xinit. Of
course that has *another* way of doing the same thing, but it's used
less often :) )

> So far, mounting "$HOME" under sshfs with;
>
> $ sshfs -o nonempty -o allow_root -o ServerAliveInterval=15 user(a)server: /home/user
>
> Has got rid of my NFS locking issues entirely, and so far every application
> (Iceweasel, OpenOffice, Icedove), has worked fine. Previously with the userspace NFS
> OpenOffice was being difficult about file locking.

Woo! :)

.... er, does sshfs implement locking at all? My understanding is that it
doesn't: you need a very recent kernel to intercept locking calls in
FUSE at all, and I don't know if sshfs has ever been updated.

> I'm guessing I'm in "less trodden ground", but that it "just worked"
> once GNOME was started gives me a bit more confidence. At least enough
> to stop exposing the NFS exports to my wireless LAN, not that I needed
> much encouragement in that area.

You'll see a big problem as soon as the server reboots, I predict :(

--
`In the future, company names will be a 32-character hex string.'
--- Bruce Schneier on the shortage of company names
From: Nix on
On 22 Feb 2007, Mike Civil spake thusly:

> In article <45dcb47b.0(a)entanet>, Simon Waters <a(a)technocool.net> wrote:
>>echo "export ICEAUTHORITY=/tmp/.ICEauthority" >>$HOME/.gnomerc
>
> OK as long as only one user ever starts an X session?

You want

mkdir "/tmp/.ICE-$(id -un)"
chmod 0700 "/tmp/.ICE-$(id -un)"
export ICEAUTHORITY="/tmp/.ICE-$(id -un)/.ICEauthority"

or something like that.

--
`In the future, company names will be a 32-character hex string.'
--- Bruce Schneier on the shortage of company names
From: Simon Waters on
> Er, why not preserve your .config?

I do, I even set the variable to allow me to get it out of /proc for when
I forget where I put it, or delete the source. However I have this vague
recollection that the reason I abandoned building a new kernel for this
box last time, was that I couldn't get a sensible config for it using my
old .config file.

> (I've
> occasionally built a kernel with the entirely-default config, but that's
> soon detectable when it utterly fails to boot :) )

Guaranteed on this server, it uses the older megaraid drivers, and the
new ones just didn't work last time I tried.

Oh well, I need to change some other kernel settings, so I guess NFS and
some VPN solution it is.

> You might want to have a look at <http://fs.net/> as well. It's sadly
> unmaintained but a really nifty idea.

Thanks, I had seen it in Debian when searching for alternative ideas for
a secure network file system.

>> So far I've mostly used sshfs, to run the wrong version of subversion
>> client, against my working copy of projects?! Don't do that.
>
> Er, oops? (mind you, svn should warn you, unless you ran a too-*new*
> version and it updated your working copy's version on you :) )

Yes, too new. I know the development box should go to Etch as well.

> Well, I'm in the jobs market after a fifth year running with no pay
> rise... :)

I'd hire you in an instant, but urm I seem to be in year three with no pay
rise :(