* Peter Cordes
| You mean Xnest?
Yes, sorry, I didn't check and recalled the wrong name.
--
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about who its friends are.
One more thing: you can also add these lines to /etc/orbitrc to make
them system-wide defaults. This file doesn't seem to be included in
Debian, I guess it's another undocumented feature.
Brian Kimball wrote:
$ cat ~/.orbitrc
ORBIIOPUSock=1
ORBIIOPIPv4=0
ORBIIOPIPv6=0
$
--
Brian Kimball
And to stop xdm's port add -udpPort 0 to /etc/init.d/xdm
something like:
start-stop-daemon --start --quiet --pid $PIDFILE --exec $DAEMON -- -udpPort 0
|| echo -n already running
or prefered in /etc/X11/xdm/xdm-config add
DisplayManager.requestPort: 0
J.Currey
On Wed, Mar 22, 2000
Brian,
Check /etc/esound/esd.conf. Change auto_spawn=1 to 0.
Also, esd has an option for using Unix sockets, but it says that they're
disabled for security reasons. Anyone have any idea why?
Regards,
Alex.
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM d- s:+ a--- C UL P L+++ E W++
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.
Brian,
That sounds like it should be filed in a bug report, wouldn't you agree?
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--
Alexander Hvostov wrote:
That sounds like it should be filed in a bug report, wouldn't you agree?
Good thinking. It looks like a similar bug has been open for a while;
I'll go tell Chris to to fix it.
--
Brian Kimball
-BEGIN PGP SIGNED MESSAGE-
On Wed, 22 Mar 2000, Alexander Hvostov wrote:
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
* Sergio Brandano
| I am using gdm. Let see how I can do that. Anyway, will this affect
| ssh?
Yes, but you can run Xev (X-in-a-window) and ssh from there. This
is safer as well if you are really paranoid, since then you trust
the remote sshd less.
--
Tollef Fog Heen
Unix _IS_ user
Yes, but you can run Xev (X-in-a-window) and ssh from there. This
is safer as well if you are really paranoid, since then you trust
the remote sshd less.
There does not seem to be a package for it. Does it come with Debian?
Sergio
On 23 Mar 2000, Tollef Fog Heen wrote:
Yes, but you can run Xev (X-in-a-window) and ssh from there. This
is safer as well if you are really paranoid, since then you trust
the remote sshd less.
Is Xev packaged for debian? If yes, what is the package, if no, where can
I find out more
On Thu, Mar 23, 2000 at 01:00:55PM +0100, Tollef Fog Heen wrote:
* Sergio Brandano
| I am using gdm. Let see how I can do that. Anyway, will this affect
| ssh?
Yes, but you can run Xev (X-in-a-window) and ssh from there. This
is safer as well if you are really paranoid, since then
Greetings,
Would anyone happen to know if it's possible (without hacking the sources
and breaking something) to disable the TCP listen ports that a great deal
of GNOME apps seem to listen on?
My suspicion is that these ports are used for GNOME's CORBA support, which
is great, but I tend to feel
Previously Alexander Hvostov wrote:
Would anyone happen to know if it's possible (without hacking the sources
and breaking something) to disable the TCP listen ports that a great deal
of GNOME apps seem to listen on?
There is some orbit-configuration file you should be able to create to
tell
Alexander Hvostov wrote:
Would anyone happen to know if it's possible (without hacking the sources
and breaking something) to disable the TCP listen ports that a great deal
of GNOME apps seem to listen on?
I have the same need. Also, the following thing occours with exactly?
the same
On Wed, Mar 22, 2000 at 01:24:31PM +, Sergio Brandano wrote:
Alexander Hvostov wrote:
Would anyone happen to know if it's possible (without hacking the sources
and breaking something) to disable the TCP listen ports that a great deal
of GNOME apps seem to listen on?
I have the
saft is controlled from /etc/inetd.conf at least it was when i somehow
I can see it depends on inetd, by running netstat -anp | egrep 487,
but i see no reference to it in the /etc/init.d files.
ended up with it. printer is lpd, /etc/init.d/lprng stop. X11 is
done!
opened whenever you
Greetings,
What about printing via a UNIX socket? Is that even supported?
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
Ingemar Fällman wrote
Start X whit the parameter '-nolisten tcp' (startx -- -nolisten tcp)
then X wont listen on port 6000
I am using gdm. Let see how I can do that. Anyway, will this affect
ssh?
Sergio
On Wed, 22 Mar 2000, Ethan Benson wrote:
Netbus and nterm, no idea.
Depending on which version you have installed on your system, the command
netstat -ap
will give you a list of the ports on which your computer is listening and
(the p switch) the process id that is listening on each of them.
Sergio Brandano wrote:
Ingemar Fällman wrote
Start X whit the parameter '-nolisten tcp' (startx -- -nolisten tcp)
then X wont listen on port 6000
in /etc/gdm/gdm.conf
add -nolisten tcp after /usr/bin/X11/X in the servers section
my config looks like this:
[servers]
#0=/usr/bin/X11/X
Ethan Benson wrote:
saft is controlled from /etc/inetd.conf at least it was when i somehow
ended up with it.
In order to kill saft I had to purge the sendfile package.
Sergio
22 matches
Mail list logo
