03-01-2014
Xterm dies after being idle
I am running eod8 to connect to a linux machine running
carnesr==>uname -a
Linux hostname 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
I have a script that opens up several xterms as follows:
/usr/bin/xterm -geometry 150x60+0-0 -name "White&Black" -fn Rom11.500 &
I notice if I don't use an xterm for a while I get the following error in the root window of the session:
White&Black: fatal IO error 110 (Connection timed out) or KillClient on X server "xxxxxx.xxx.xxx.xxxx.com:16.0"
Any idea what is controlling this and how to stop it from happening ?
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi folks,
anybody there with suggestions on how to have an email sent to an address (if a certain job (jobA) ever dies. the concern is over the trigerring of sending the email (not the actual sending of the email)
1. is it possible for the job in question, jobA, itself do such a thing... (2 Replies)
Discussion started by: jacob_gs
2 Replies
2. Solaris
Say I have a daemon that dies for an unknown reason. Is there a way to track its process ID to try to determine when it dies and what causes it to go away? (2 Replies)
Discussion started by: Silver11
2 Replies
3. SCO
We have just installed a sco 600 server. Xdmcp comes up in the chooser but if you don't log in within a few minutes it disappears and you have to log in
and then out on the console before you can see it in the chooser. Xdmcp is
suppossed to be setup for continuous logins automatically. We... (0 Replies)
Discussion started by: khafner
0 Replies
4. Windows & DOS: Issues & Discussions
Hello All: I hope this is the right category...
I have a application (this app runs under java and jboss) that runs under Windows, it's started as a service. If that application should become disabled, crash or no longer function, what would be the best method for determining it is no longer... (6 Replies)
Discussion started by: jimmyc
6 Replies
5. Solaris
I noticed for some time now on solaris 8 whenever our root or oracle password expires after 12 weeks the cronjob for the expired user will totally stop working, it will start working again once the password has been changed.
I wonder if anybody encountered this problem and knows of a fix other... (4 Replies)
Discussion started by: sparcguy
4 Replies
6. UNIX for Advanced & Expert Users
Hi,
I have over 5 gb of data in a files structure in which month folders are in year folders, day folders are in month folders, and individual climate stations are in each day. I am trying to extract precipitation measured at 5 minute intervals for a duration of 15 years, but the script never... (2 Replies)
Discussion started by: mlw63@me.com
2 Replies
7. IP Networking
We have a NAS application which can be accessed by both HTTP and HTTPS connections.
The issue we are facing is that the tcp server instance that initiates the HTTP access dies after a few hours of inactivity(the NAS application was kept idle for around 10 hours). However, the tcpserver that... (1 Reply)
Discussion started by: swatidas11
1 Replies
8. Hardware
Hello,
I am having a problem with my wireless. Seems to be a relatively new problem over the past few weeks. I have an intel wireless. It seems like it can be fine for days, then in will quite working to the point a reboot is necessary. It may happen once and be fine, or may happen several times... (0 Replies)
Discussion started by: Narnie
0 Replies
9. HP-UX
After install of the Sept. 2010 patch set on my hpux 11.23 system, my xterm when launched, dies immediately on the client with the xserver, with a core.xterm file in root of the hpux server. This had been working before the patch install.
I tried to find xterm patches from ITRC (yes the old... (1 Reply)
Discussion started by: mrmurdock
1 Replies
LEARN ABOUT CENTOS
reposync
reposync(1) reposync(1)
NAME
reposync - synchronize yum repositories to a local directory
SYNOPSIS
reposync [options]
DESCRIPTION
reposync is used to synchronize a remote yum repository to a local directory, using yum to retrieve the packages.
OPTIONS
-h, --help
Display a help message, and then quit.
-c CONFIG, --config=CONFIG
Config file to use (defaults to /etc/yum.conf).
-a ARCH, --arch=ARCH
Act as if running the specified arch (default: current arch, note: does not override $releasever. x86_64 is a superset for i*86.).
--source
Also download .src.rpm files.
-r REPOID, --repoid=REPOID
Specify repo ids to query, can be specified multiple times (default is all enabled).
-t, --tempcache
Use a temp dir for storing/accessing yum-cache.
-p DESTDIR, --download_path=DESTDIR
Path to download packages to: defaults to current directory.
-g, --gpgcheck
Remove packages that fail GPG signature checking after downloading. exit status is '1' if at least one package was removed.
-u, --urls
Just list urls of what would be downloaded, don't download.
-l, --plugins
Enable yum plugin support.
-n, --newest-only
Download only newest packages per-repo.
-q, --quiet
Output as little information as possible.
EXAMPLES
Sync all packages from the 'updates' repo to the current directory:
reposync --repoid=updates
Sync only the newest packages from the 'updates' repo to the current directory:
reposync -n --repoid=updates
Sync packages from the 'updates' and 'extras' repos to the current directory:
reposync --repoid=updates --repoid=extras
Sync all packages from the 'updates' repo to the repos directory:
reposync -p repos --repoid=updates
Sync all packages from the 'updates' repo to the repos directory excluding x86_64 arch. Edit /etc/yum.conf adding option exclude=*.x86_64.
Then:
reposync -p repos --repoid=updates
FILES
reposync uses the yum libraries for retrieving information and packages. If no configuration file is specified, the default yum configura-
tion will be used.
/etc/yum.conf
/etc/yum/repos.d/
SEE ALSO
yum.conf (5)
http://yum.baseurl.org/
AUTHORS
See the Authors file included with this program.
BUGS
There are of course no bugs, but should you find any, you should first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and if
unsuccessful in finding a resolution contact the mailing list: yum-devel@lists.baseurl.org. To file a bug use http://bugzilla.redhat.com
for Fedora/RHEL/Centos related bugs and http://yum.baseurl.org/report for all other bugs.
27 April 2007 reposync(1)