10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hello and thanks in advance for any assistance anyone can offer me
The fast & dirty question is... Could someone please tell me which file would open an xterm session into $HOME/Desktop instead of /$HOME?
The longer version is.... I was reading about login scripts when I noticed my SSH... (3 Replies)
Discussion started by: bodisha
3 Replies
2. Red Hat
Hi,
I am using Xming tool to open the my RHEL machine remotely in UI mode. When I use xclock command using 'root', the command works properly and I can see the clock pop-up. However, when I run the 'xclock' command using oracle user I get an error, which is shown in the attached file.
Can... (6 Replies)
Discussion started by: omniok
6 Replies
3. Solaris
This is where I am getting stuck and I am wondering if I can get some help from the community.
I log into putty with X11 forward enable
echo $DISPLAY
DISPLAY=localhost:10.0
export DISPLAY
xclock ( I do see a clock)
:)
I am happy that I finally get to install Oracle 11g on solaris... (2 Replies)
Discussion started by: newborndba
2 Replies
4. Shell Programming and Scripting
Hi, I have written a script that allows me to repetitively play a music file $N times, which is specified through user input. However, if I want to exit the script before it has finished looping $N times, if I use CTRL+c, I have to CTRL+c however many times are left in order to complete the loop.... (9 Replies)
Discussion started by: hilltop_yodeler
9 Replies
5. Red Hat
hi rhel6 gurus
i have set up a rhel6.2 db server.
i have data base admins needing to connect to this rhel6 derver via reflectionx. reflectionx is set correctly but when attempting to test connectivity by 'xclock' the following message pops up : -bash:xclock; command not found.
anyone out... (1 Reply)
Discussion started by: jsynodin
1 Replies
6. Shell Programming and Scripting
Hey all, I need to launch a script from within 2 other scripts that can run independently of the two parent scripts... Im having a hard time doing this, if anyone knows how please let me know.
More detail.
ScriptA (bash), ScriptB (ksh), ScriptC (bash)
ScriptA, launches ScriptB
ScirptB,... (7 Replies)
Discussion started by: trey85stang
7 Replies
7. UNIX for Advanced & Expert Users
Hi folks,
I would like to know how to hook up an xterm to another process.
Here is a high level view of what I am looking for
1. Main program starts
2. It creates an new xterm window
3. It then forks a second process & passes the xterm handle to it
4. The second process uses the second... (4 Replies)
Discussion started by: RipClaw
4 Replies
8. Shell Programming and Scripting
Hi
I want to do something that might sound strange.
I have a code that in written in C and is executed at startup (it's a custom process). It occasionally calls some bash scripts.
The process doesn't have any terminal associated with it.
One thing I don't know how to do is to start a... (5 Replies)
Discussion started by: alirezan
5 Replies
9. Shell Programming and Scripting
Hi everyone,
could you explain why am I not able to bring up xclock, or for that matter any Xtools (xcalc etc...), in the background?
When I execute:
xclock &
This brings up the clock in the foreground, my focus is on the clock, not back in my command window.
Any suggestion?
... (2 Replies)
Discussion started by: gio001
2 Replies
10. Linux
When I telnet (ssh) over to my Fedora system, I find the colors horrible. For instance, regular files are white text, which is fine, but directories show up as dark blue which is virtually invisible against the black background). Additionally, when using vi, I find the colors great doing perl... (3 Replies)
Discussion started by: ripley
3 Replies
XINIT(1) General Commands Manual XINIT(1)
NAME
xinit - X Window System initializer
SYNOPSIS
xinit [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]
DESCRIPTION
The xinit program is used to start the X Window System server and a first client program on systems that are not using a display manager
such as xdm(1) or in environments that use multiple window systems. When this first client exits, xinit will kill the X server and then
terminate.
If no specific client program is given on the command line, xinit will look for a file in the user's home directory called .xinitrc to run
as a shell script to start up client programs. If no such file exists, xinit will use the following as a default:
xterm -geometry +1+1 -n login -display :0
If no specific server program is given on the command line, xinit will look for a file in the user's home directory called .xserverrc to
run as a shell script to start up the server. If no such file exists, xinit will use the following as a default:
X :0
Note that this assumes that there is a program named X in the current search path. The site administrator should, therefore, make a link
to the appropriate type of server on the machine, or create a shell script that runs xinit with the appropriate server.
Note, when using a .xserverrc script be sure to ``exec'' the real X server. Failing to do this can make the X server slow to start and
exit. For example:
exec Xdisplaytype
An important point is that programs which are run by .xinitrc should be run in the background if they do not exit right away, so that they
don't prevent other programs from starting up. However, the last long-lived program started (usually a window manager or terminal emula-
tor) should be left in the foreground so that the script won't exit (which indicates that the user is done and that xinit should exit).
An alternate client and/or server may be specified on the command line. The desired client program and its arguments should be given as
the first command line arguments to xinit. To specify a particular server command line, append a double dash (--) to the xinit command
line (after any client and arguments) followed by the desired server command.
Both the client program name and the server program name must begin with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines. This makes it possible to add arguments (for example, foreground and back-
ground colors) without having to retype the whole command line.
If an explicit server name is not given and the first argument following the double dash (--) is a colon followed by a digit, xinit will
use that number as the display number instead of zero. All remaining arguments are appended to the server command line.
EXAMPLES
Below are several examples of how command line arguments in xinit are used.
xinit This will start up a server named X and run the user's .xinitrc, if it exists, or else start an xterm.
xinit -- /usr/local/bin/Xvnc :1
This is how one could start a specific type of server on an alternate display.
xinit -geometry =80x65+10+10 -fn 8x13 -j -fg white -bg navy
This will start up a server named X, and will append the given arguments to the default xterm command. It will ignore .xinitrc.
xinit -e widgets -- ./Xorg -l -c
This will use the command .Xorg -l -c to start the server and will append the arguments -e widgets to the default xterm command.
xinit /usr/ucb/rsh fasthost cpupig -display ws:1 -- :1 -a 2 -t 5
This will start a server named X on display 1 with the arguments -a 2 -t 5. It will then start a remote shell on the machine
fasthost in which it will run the command cpupig, telling it to display back on the local workstation.
Below is a sample .xinitrc that starts a clock, several terminals, and leaves the window manager running as the ``last'' application.
Assuming that the window manager has been configured properly, the user then chooses the ``Exit'' menu item to shut down X.
xrdb -load $HOME/.Xresources
xsetroot -solid gray &
xclock -g 50x50-0+0 -bw 0 &
xload -g 50x50-50+0 -bw 0 &
xterm -g 80x24+0+0 &
xterm -g 80x24+0-0 &
twm
Sites that want to create a common startup environment could simply create a default .xinitrc that references a site-wide startup file:
#!/bin/sh
. /usr/local/lib/site.xinitrc
Another approach is to write a script that starts xinit with a specific shell script. Such scripts are usually named x11, xstart, or
startx and are a convenient way to provide a simple interface for novice users:
#!/bin/sh
xinit /usr/local/lib/site.xinitrc -- /usr/bin/X -br
ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect.
XINITRC This variable specifies an init file containing shell commands to start up the initial windows. By default, .xinitrc in the
home directory will be used.
FILES
.xinitrc default client script
xterm client to run if .xinitrc does not exist
.xserverrc default server script
X server to run if .xserverrc does not exist
SEE ALSO
X(7), startx(1), Xserver(1), Xorg(1), xorg.conf(5), xterm(1)
AUTHOR
Bob Scheifler, MIT Laboratory for Computer Science
X Version 11 xinit 1.3.2 XINIT(1)