I have Master script, Main script ,and 4 Child script.
Master.sh
Main.sh
I run only Master.sh script because Master.sh calls Main.sh and Main.sh calls 4 Child.sh (need run parallel)
After I ran Master.sh,I get message "Killed by signal 15."
I'm not sure that root cause is input "&" ?
I have a process that is in the sleeping state "S" and I have tried to stop it with a run control script that I use to stop/start it - but it does not stop.
I have tried kill -9 <PID of process> with no change. I imagine that this process is sleeping with the kernel.
It does not respond to... (5 Replies)
UPDATE: I think I may have a culprit. I had KDE console history to unlimited, and since there's a lot of output... I'm thinking that may be it. I'd still like to hear advice on how to figure out why processes get killed, if anyone has any! though
******************
There's this script I run... (1 Reply)
Hi,
We are using oracle 10g in a Solaris box. The same box has Informatica also installed. But it runs on port 6001. But whenever the server is restarted the Oracle database picks up the port 6001 and does not allow Informatica to be started. But I am have no clue of which Oracle process is... (2 Replies)
hey champs,
I have a process running.......i have to catch/trap the signal when the process is being interupted/killed (kill -9 pid) option......
how can i achieve the same thru my process........
let my process is a.sh and it supposed to take 13 mins to complete, but due to some problem ,... (15 Replies)
Hi There,
Hope anyone can give me a hand on AIX
oslevel -r
5300-05
Try to "ls *sh" from folder and it return killed, is there any clue on that?
1. perform ls and count
ls * | wc -l
0
ksh: 561582 Killed
2. without provide "*" wildcard, the result can be return
ls | wc
... (7 Replies)
Can anyone explain?
I start my unix session on AIX, run tcsh move to a particular directory, let say: cd /test/bin and next i run a command like:
grep "test string" /test/bin/*
to look for the string in any files in the directory.
I am getting a response of Killed.
Why is that... (16 Replies)
Hi All,
I am running synsort utility via unix scripts.
As soon as the control reaches the syncsort command,Its getting killed.
The error message is
/proj/cdw/syncsort/dev/copay/CdwWkRvrslFileReformat.syn: 8339696 Killed
. Please suggest to overcome this issue. (5 Replies)
hey,
i have been facing a very fatel error with dovecot..
i am getting this error in my dovecot.log file
dovecot: Feb 13 15:21:02 Fatal: chdir(/var/mail/folders/user1) failed with uid 1001: Permission denied
dovecot: Feb 13 15:21:02 Error: child 18732 (imap) returned error 89
dovecot: Feb... (3 Replies)
Has Oracle killed HP-UX with their gambit of telling the public they would no longer support Itanium? The company I work for in the Dallas, TX area has had several openings for HP-UX administrators and we're having such a tough time finding qualified people to fill them. I have been searching job... (3 Replies)
Hi,
i have 2 machines in ESXI6 that both made a restart at the same time but no errors from ESXI side.
one machine with Centos 6.6 and one with centos 7
same log at the Dmesg:
please help me find a lead what could made this ?
Mar 17 20:20:28 pbxnl-b-sales-ru-ua init: tty (/dev/tty1) main... (2 Replies)
Discussion started by: batchenr
2 Replies
LEARN ABOUT REDHAT
pam_xauth
pam_xauth(8) System Administrator's Manual pam_xauth(8)NAME
pam_xauth - forward xauth keys between users
SYNOPSIS
session optional /lib/security/pam_xauth.so arguments
DESCRIPTION
pam_xauth.so is designed to forward xauth keys (sometimes referred to as "cookies") between users.
Without pam_xauth, when xauth is enabled and a user uses the su command to assume another user's priviledges, that user is no longer able
to access the original user's X display because the new user does not have the key needed to access the display. pam_xauth solves the
problem by forwarding the key from the user running su (the source user) to the user whose identity the source user is assuming (the target
user) when the session is created, and destroying the key when the session is torn down.
This means, for example, that when you run su from an xterm sesssion, you will be able to run X programs without explicitly dealing with
the xauth command or ~/.Xauthority files.
pam_xauth will only forward keys if xauth can list a key connected to the $DISPLAY environment variable.
Primitive access control is provided by ~/.xauth/export in the invoking user's home directory and ~/.xauth/import in the target user's home
directory.
If a user has a ~/.xauth/import file, the user will only receive cookies from users listed in the file. If there is no ~/.xauth/import
file, the user will accept cookies from any other user.
If a user has a .xauth/export file, the user will only forward cookies to users listed in the file. If there is no ~/.xauth/export file,
and the invoking user is not root, the user will forward cookies to any other user. If there is no ~/.xauth/export file, and the invoking
user is root, the user will not forward cookies to other users.
Both the import and export files support wildcards (such as *). Both the import and export files can be empty, signifying that no users
are allowed.
ARGUMENTS
debug Turns on debugging messages sent to syslog.
xauthpath=/usr/X11R6/bin/xauth
Specify the path the xauth program (the default is /usr/X11R6/bin/xauth).
IMPLEMENTATION DETAILS
pam_xauth will work only if it is used from a setuid application in which the getuid() call returns the id of the user running the applica-
tion, and for which PAM can supply the name of the account that the user is attempting to assume. The typical application of this type is
su. The application must call both pam_open_session() and pam_close_session() with the ruid set to the uid of the calling user and the
euid set to root, and must have provided as the PAM_USER item the name of the target user.
pam_xauth calls xauth as the source user to extract the key for $DISPLAY, then calls xauth as the target user to merge the key into the a
temporary database and later remove the database.
pam_xauth cannot be told not to remove the keys when the session is closed.
SEE ALSO
/usr/share/doc/pam*/html/index.html
FILES
~/.xauth/import ~/.xauth/export
BUGS
Let's hope not, but if you find any, please report them via the "Bug Track" link at http://bugzilla.redhat.com/bugzilla/
AUTHOR
Nalin Dahyabhai <nalin@redhat.com>, based on original version by Michael K. Johnson <johnsonm@redhat.com>
Red Hat Linux 2001/9/27 pam_xauth(8)