xdmcp dies in sco600

9 More Discussions You Might Find Interesting

1. HP-UX

Xterm display immediatly dies in hpux 11.23

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...

2. UNIX for Advanced & Expert Users

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...

3. Hardware

Wireless works, then dies requiring a reboot

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...

4. IP Networking

TCP server dies after few hours of inactivity

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...

5. UNIX for Advanced & Expert Users

script dies prematurely and unpredictably

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...

6. Solaris

cronjob dies when user password expires

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...

7. Windows & DOS: Issues & Discussions

How to detect if a Windows app dies??

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...

8. Solaris

daemon dies, need to know why

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?

9. Shell Programming and Scripting

email notification if job is killed/dies

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...

LEARN ABOUT DEBIAN

mergelogs

MERGELOGS(1)						      General Commands Manual						      MERGELOGS(1)

NAME

       mergelogs - merge and consolidate web server logs

SYNOPSIS

       mergelogs -p penlog [-c] [-d] [-j jitter] [-t seconds] server1:logfile1 [server2:logfile2 ...]

EXAMPLES

       mergelogs -p pen.log 10.0.0.1:access_log.1 10.0.0.2:access_log.2

       mergelogs -p pen.log 10.0.18.6:access_log-10.0.18.6 10.0.18.8:access_log-10.0.18.8

DESCRIPTION

       When pen is used to load balance web servers, the web server log file lists all accesses as coming from the host running pen. This makes it
       more difficult to analyze the log file.

       To solve this, pen creates its own log file, which contains the real client address, the time of the access, the target server address  and
       the first few bytes of the requests.

       Mergelogs reads pen's log file and the log files of all load balanced web servers, compares each entry and creates a combined log file that
       looks as if the web server cluster were a single physical server.  Client addresses are replaced with the real client addresses.

       In the event that no matching client address can be found in the pen log, the server address is used instead. This should never happen, and
       is  meant  as  a debugging tool. A large number of these indicates that the server system date needs to be set, or that the jitter value is
       too small.

       You probably don't want to use this program. Penlog is a much more elegant and functional solution.

OPTIONS

       -c     Do not cache pen log entries. The use of this option is not recommended, as it will make mergelogs search the  entire  pen  log  for
	      every line in the web server logs.

       -d     Debugging (repeat for more).

       -p penlog
	      Log file from pen.

       -j jitter
	      Jitter  in  seconds (default 600). This is the maximum variation in time stamps in the pen and web server log files. A smaller value
	      will result in a smaller pen log cache and faster processing, at the risk of missed entries.

       -t seconds
	      The difference in seconds between the time on the pen server and UTC.  For example, this is 7200 (two hours) in Finland.

       server:logfile
	      Web server address and name of log file.

AUTHOR

       Copyright (C) 2001-2003 Ulric Eriksson, <ulric@siag.nu>.

SEE ALSO

       pen(1), webresolve(1), penlog(1), penlogd(1)

								       LOCAL							      MERGELOGS(1)

SCO