log session Post: 302165998

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

sqlplus session being able to see unix variables session within a script

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. Shell Programming and Scripting

Hiding Directories on a Session by Session basis

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

I am not able to login in gnome session and java session in Sun solaris 9& 10

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

4. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also?

5. Shell Programming and Scripting

Determining if session is a login session

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.

6. Solaris

Difference between the desktop session and console session

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

7. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN...

8. Linux

Session "hijacking" - Recover lost session

Hi Guys, Is there a way to recover a lost session? I was working in a server and that lost the connection, now, I have a new session but all the previous processes that I was running, like scripts, etc, are still running. Is there a way to bring them to my session? Best regards, Marco.

9. Shell Programming and Scripting

[Solved] The SCRIPT command - Can we see the log file of a running session?

Hello. This is my situation. script .anything ls -l . ---How can I see the content of .anything using (i.e) cat .anything? If not possible can someone suggest a sequence to simulate a console-recorder to "observ" from a RUNNING script session? Thanks Paolo Please use code tags...

LEARN ABOUT OSF1

lsmsad

lsmsad(8)						      System Manager's Manual							 lsmsad(8)

NAME

       lsmsad - Starts the Storage Administrator (SA) daemon

SYNOPSIS

       /usr/sbin/lsmsad

DESCRIPTION

       The SA daemon, lsmsad, is a process required by lsmsa, the SA graphical user interface (GUI). The daemon issues commands and obtains system
       information on behalf of SA.

       The SA daemon runs on a Tru64 UNIX system on which LSM is initialized and running.  The SA client runs on any  machine  that  supports  the
       Java Runtime Environment.

       The SA daemon is automatically started at boot time. Under normal conditions, the daemon does not need to be run manually.

       If SA does not start during the boot process, enter:

       /sbin/init.d/lsmsa stop

       To restart SA, enter:

       /sbin/init.d/lsmsa start

       Only one SA daemon can be running on a system at a given time. If a second SA daemon attempts to start, it will fail.

RESTRICTIONS

       You must be root user to run lsmsad.

FILES

       The script that starts lsmsad at boot time.  The command log file that tracks SA tasks.	The access log file that tracks login to  SA.  The
       server log file that tracks server startup information and server errors.  The log maintenance shell script that saves and  compresses  log
       files.

SEE ALSO

       lsmsa(8), volintro(8)

																	 lsmsad(8)