|
|
Sponsored Content
Operating Systems
Linux
Red Hat
Session Logging
Post 302759703 by fpmurphy on Tuesday 22nd of January 2013 07:37:57 PM
01-22-2013
|
|
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there.
How do I make the DB connection see the parameter variables passed to the unix script ? The code snippet below isn't working properly.
sqlplus << EOF
user1@db1/pass1
BEGIN
PACKAGE1.perform_updates($1,$2,$3);
END;
EOF
Thanks in advance,
Abrahao. (2 Replies)
Discussion started by: 435 Gavea
2 Replies
2. Shell Programming and Scripting
Hi,
Apologies if anyone has read my recent post on the same subject in the Linux forum, just thought actually the solution might more likely come from scripting.
Essentially, I am trying to restrict access to directories based on the user's name AND their location on a session-by-session... (3 Replies)
Discussion started by: en7smb
3 Replies
3. Solaris
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies
4. UNIX for Advanced & Expert Users
Is it possible to have a user session logged as an AIX process or initiated as a sub server? Can anyone please help?
Gayathri (0 Replies)
Discussion started by: ggayathri
0 Replies
5. Shell Programming and Scripting
I'm looking at allowing remote telnet into my server.
like any security-minded administrator, I want to log what my users type on the telnet session.
I'm using the script command to generate transcripts of the users session.
I have /etc/profile set to automatically start the script command... (2 Replies)
Discussion started by: ramnet
2 Replies
6. Shell Programming and Scripting
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
Discussion started by: jgt
3 Replies
7. Solaris
what is the difference between desktop session and console session in solaris
as i am wondering we use option -text for the former and -nowin for the later (1 Reply)
Discussion started by: kishanreddy
1 Replies
8. Shell Programming and Scripting
HI ,
I have a simple script that moves files from one folder to another folder, I have already done the open-ssh server settings and the script is working fine and is able to transfer the files from one folder to another but right now I myself execute this script by using my creditianls to... (4 Replies)
Discussion started by: nks342
4 Replies
9. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
LEARN ABOUT CENTOS
ksc
KSC(1) User Commands KSC(1) NAME
ksc - Linux kernel module source checker SYNOPSIS
ksc [ -d | --directory ] DIRECTORY ksc [ -k | --ko ] FILE OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it checks for the specific architecture for which the binary was built. Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4 -h, --help show this help message and exit -c CONFIG, --config=CONFIG path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from /etc/ksc.conf -d DIRECTORY, --directory=DIRECTORY path to the directory -i, --internal to create text files to be used internally. -k KO, --ko=KO path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the same time then only -d is used and the -k option is discarded. -n RELEASENAME, --name=RELEASENAME Red Hat release against which the bug is to be filed. Default value is 6.5 -p PREVIOUS, --previous=PREVIOUS path to the previous resultset file and submit it as a bug to Red Hat Bugzilla. -r RELEASE, --release=RELEASE RHEL whitelist release used for comparison -s, --submit Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The tool will prompt for bugzilla password. The configuration file looks like below: [bugzilla] user=user@redhat.com partner=partner-name partnergroup=partner-group server=https://bugzilla.redhat.com/xmlrpc.cgi -v, --version Prints KSC version number ksc - Version 0.9.11 Feb 2014 KSC(1)