1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
Notes on Viewglob
-----------------
1) Refocusing problems on some terminals
Some terminals (notably gnome-terminal and maybe konsole) do not play well
with Viewglob. If you run viewglob in more than one of these terminals at
a time, the vgseer window will not automatically switch between terminals
when you change terminal focus. To force it to do so, press <Ctrl>-g
followed by <Tab> in the desired terminal window. See the USAGE section
of the viewglob(1) man page for more information.
2) A comment on security
As of Viewglob version 2.0.2, the vgseer client and the viewglob
script will by default use local Unix sockets to communicate with a vgd
daemon. Since vgd creates these sockets in the directory $HOME/.viewglob/,
a vgseer client connecting to a vgd daemon by Unix sockets is guaranteed to
be "safe". The sockets are named ".<number>"; if you have more than one
vgd active, you can tell the viewglob script which socket to use with the
--port=<number> flag.
If necessary, you can connect a vgseer to a vgd on a TCP port instead.
This will happen when either you give vgseer the --unix-socket=off flag (in
which case it will connect to localhost on the specified port, if --port is
given, or otherwise port 16108), or when you give viewglob or vgseer the
--host flag to specify a remote host. If you do so, be very certain that
the vgd process to which you connect is also under your control; otherwise
another user could spy on your vgseer window.
-- Kevin B. McCarty <kmccarty@debian.org>, Sun, 3 Jul 2005
|
