Hi,
i willbe very much grateful to u if u help me out..
if i simply connect pbx machine to printer by serial port RS232 then we find this view:
But i want to capture this data into database automatically when the pbx is running.The table in database will contain similar to this view inthe... (1 Reply)
Hi,
I have installed oracle 9i on solaris 10 sucessfully. I have configured listener & tnsname.ora file sucessfuly. Even i can start database manully by starting listener first and from sqlplus promt data base sucessfully. Now i want to start the database automatically after system reboots.
I... (2 Replies)
Hello All
i have a question related to some services,i want to start some services with server linux centos.
i make "chkconfig httpd on" and "chkconfig asterisk on",but when i verify with chkconfig --list i found
httpd 0: off 1: off 2: on 3: on 4: on 5: on 6:... (6 Replies)
I installed Oracle 10 software on Solaris 11 Express, everything was fine execpt I can't create database using dbca.rsp file. I populated file with following options.
OPERATION_TYPE = "createDatabase"
GDBNAME = "solaris_user.domain.com"
SID = "solaris_user"
TEMPLATENAME = "General... (0 Replies)
Hi Guys,
Need you help in one point!
I am working on one shell script which takes following steps :
1. Taking one query result from oracle database
2. Exporting that result to Xls file
3. Mailing that file to my own mail ID
Now, I want to give a threshold limit to one of the column... (0 Replies)
Good evening
I nned your help pls, In an unix server i want to connect to a remote oracle databse server by sqlplus.
I tried to find out the user/passwd and service name by env variable and all Ive got is this:
ORACLE_SID_REPCOL=SCL_REPCOL
ORACLE_SID=xmeta
ORACLE_SID_TOL=SCL_PROTOLCOL... (2 Replies)
Discussion started by: alexcol
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)