summaryrefslogtreecommitdiff
path: root/astro/setiathome/files/xsetiathome.1
blob: 2e4849407b57f60052c6420b3d1295af352a3a40 (plain) (blame)
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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
.\" $FreeBSD$
.Dd Feb 13, 2000
.Dt xsetiathome 1 LOCAL
.Os FreeBSD
.Sh NAME
.Nm xsetiathome
.Nd display SETI data under X Windows
.Sh SYNOPSIS
.Nm
.Op Fl fullscreen
.Sh DESCRIPTION
.Nm
is a graphical display for
.Xr setiathome 1 .
To use it you must run
.Xr setiathome 1
with the
.Fl graphics
flag. 
.Pp
A typical invocation of
.Nm
will look like this:
.Bd -literal -offset indent
% setiathome -graphics &
% xsetiathome
.Ed
.Pp
Alternatively,
.Nm
can be executed in screensaver mode,
which requires an external application such as
.Xr xautolock 1 .
.Sh OPTIONS
.Bl -tag -width fullscreenx
.It Fl fullscreen
Take over the entire display.
When running in this mode, any mouse presses will exit the application.
.El
.Sh SEE ALSO
.Xr setiathome 1
.Sh BUGS
Please note, this
.Nm
binary is an initial experiment.
We are fully aware that it may have some significant bugs and
we are continuing to work on it.
Please do not report bugs on this binary at this time.
.Pp
Only one instance of
.Ic setiathome -graphics
can be operating at any one time on a system.
There is no conflict resolution with the allocated shared memory
segments and semaphores.
Therefore, only one instance of
.Nm
is practical.
.Pp
Outstanding shared memory segments and semaphores may be left
active in case of an abnormal exit of the
.Ic setiathome -graphics
process.
These can prevent any future invocation of
.Ic setiathome -graphics .
To resolve this problem, use
.Xr ipcs 1
and
.Xr ipcrm 1
to remove shared memory segments and semaphores that
are not associated with a process.
This behavior may vary depending upon how your
.Ux
system handles this situation.
.Pp
The
.Nm
process may affect system performance adversely.
This behavior may vary depending upon your version of the
X11 Window System client libraries and/or your X server
and its operating mode/visual depth.