Brian (and everyone, for that matter), I configured ORBit to use Unix sockets as you said to do. A pleasant side effect of this is that GNOME seems to be faster.
An unpleasant side effect is that ORBit is now placing sockets in /tmp, which looks like it may be vulnerable to a symlink attack. Anyone have any idea about this? ...Shouldn't the sockets just be in the user's home directory? Regards, Alex. -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCM d- s:+ a--- C++++ UL++++ P L+++ E W++ N o-- K- w O--- M- V- PS+ PE- Y PGP t+ 5 X- R tv+ b DI--- D+ G e-- h++ r--- y ------END GEEK CODE BLOCK------ On Wed, 22 Mar 2000, Brian Kimball wrote: > Wichert Akkerman wrote: > > > There is some orbit-configuration file you should be able to create to > > tell it not to listen to TCP ports. From what I hear that kill all ports > > but one. And unfortunately it seems to be completely undocumented (I > > can't even find what filename to use..). > > $ cat ~/.orbitrc > ORBIIOPUSock=1 > ORBIIOPIPv4=0 > ORBIIOPIPv6=0 > $ > > I think this came up on a gnome mailing list a while ago. > > gnome-session and esd still listen to TCP ports. This is rather > annoying since I've disabled "sound server startup" in gnome's control > center, so esd shouldn't even be running. Grrr. > > -- > Brian Kimball > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >