DF output via SSH Post: 40319

Sponsored Content

Operating Systems BSD DF output via SSH Post 40319 by Perderabo on Friday 12th of September 2003 01:19:56 PM

09-12-2003

Administrator Emeritus

Here is what I know so far....

First, the PuTTY connection did things correctly. There you are logged in as as a real user. You have pty assigned so you can run tty type programs like vi. The login process also gave you a shell of -ksh. The leading minus sign tells the shell to run your login scripts. And somewhere in your login scripts (probably either .profile or .env) is an alias changing df to df -k.

Your wodSSH connection is a mess. No login scripts were run (explaining the difference you see with df). You're right that you can just
type:
alias df="df -k"
to fix that. And you can tidy up any other aliases or envirornment problems as well. But there is no reasonable way for you to allocate a pty for yourself. That is terrible... you can't run any full screen editors or other full screen programs. You're going to want to fix that.

Redhat reports df in k as a default...no need for your login scripts to succeed. But you may not have a pty when you connect to redhat via wodSSH.

wodSSH could have one of several possible problems. Neither of us knows your system well enough to tell which it is.

It would be sweet if you have the same problem with Redhat since I do know that well enough to track this down (well, maybe). So try to connect to Redhat from wodSSH and type "tty" If you get the message, "not a tty", then your connection to redhat is screwed up too. If so type:
ps -fp $PPID
and post the results of that. What we need to find out is the name of the parent of your shell. It might be sshd or it might be something else. Or if anyone you know can help you find out the name of the parent of your shell on OpenBSD that would work too.

I can only think of two ways for this happen, and the name of the parent will tell me which it is.

Perderabo

View Public Profile for Perderabo

Find all posts by Perderabo

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script that Redirect SSH output via cron

Hi, I have a script that's being called via a crontab which is a wrapper script that creates a log for the script that gets executed. Within the script that gets executed, it also run's subscripts. I've been able to get everything to work .. but the issue is one of the subscript that goes out...

2. Shell Programming and Scripting

Piped output from SSH tunnel hangs?

Hi All, When starting an SSH tunnel, piped output 'hangs' (on AIX) : ssh -Nf -Llocalhost:22000:server:22 proxy | cat -vet - ... hangs ... Does anybody know how to prevent this? Of course, in my script I don't use the tunnel as I do in the example above. In my script the call to ssh is...

3. Shell Programming and Scripting

how to format ssh top output

Hello; Am trying to generate runaway proc report using ssh thusly: =================== ssh -t -t $BOX 'TERMINAL="vt100" top -d1 -h -n 10' >> $FILE . . cat $FILE | mail -s "Latest Top `date`" $MAIL_TO ==================== But the output to e-mail comes out rather garbled .. Any ideas...

4. Shell Programming and Scripting

Weird tail output over ssh

Hello; Am trying to correct the formatting of tail output over ssh. Using the following code: echo "" > $FILE for BOX in $SERVERS do echo "Processing on $BOX" |tee -a $FILE echo "===============================" >> $FILE sudo ssh $BOX 'TERMINAL="vt100" /usr/bin/sh -s' <...

5. Shell Programming and Scripting

Seeing output of command over ssh

Hey Guys, i have a script that generates logs at our isilon storage. The part of the script is to geneate logs and grep its name: VAR=`ssh -o UserKnownHostsFile=/dev/null root@XXX isi_gather_info | grep -i "Package:" | awk '{ print $2 }'` Now , while this is run, i do not see the status of...

6. Shell Programming and Scripting

SSH - remote output locally

The code below works ok, however; I need to output the results to a local variable the_path="/mnt/back/hang" ssh -T -i /home/buddy/.ssh/id_rsa buddy@ginger << EOF find ${the_path} -name "*.jpg" | wc -l > ## output to local variable exit EOF

7. Shell Programming and Scripting

Error in SSH output.

Hi All, I am using below command in a shell script. ssh -q RemoteUser@RemoteServer "/export/sctipt/test.ksh" It is executing succesfully but the below is the output getting displayed. tset: standard error: Invalid argument Can you please help me in understanding below. ...

8. Shell Programming and Scripting

Getting SSH Output From Remote to Local Session?

Hi everyone, after about 2 days of scratching my head on this one, I'm finally ready to punt this and ask for some actual help. Here's the situation. We have 1 server, that runs multiple VM's. To gain access to those VM's we ssh from host01 to the other vm hosts. For example when we first log...

9. Shell Programming and Scripting

Ssh output

Hi, I need to get the output of ssh for multiple servers using for loop which is returning how many users are logged in, one below the other. But i'm getting output in single line for one of the servers. XXXX pts/0 Oct 18 08:45 abcd pts/3 Oct 18 06:46 abcde pts/4 Oct 18 06:46 xyzqw pts/5 Oct 18...

10. Shell Programming and Scripting

Read several variables from command output via SSH

Hi Folks, I'm currently trying to read several values into different variables. Actually, what I'm doing works, but I get an error message. My attempts are: read strCPROC strIPROC strAPROC <<<$(ssh -n -T hscroot@$HMC "lshwres -r proc -m $strIDENT --level sys -F \"configurable_sys_proc_units...

LEARN ABOUT DEBIAN

ttysnoops

TTYSNOOP(8)						    BSD System Manager's Manual 					       TTYSNOOP(8)

NAME

     ttysnoop -- snoop on a user's tty

SYNOPSIS

     ttysnoop [pty]
     ttysnoops

DESCRIPTION

     The ttysnoop / ttysnoops client-server combo can be used to snoop (watch) on a user's login tty.  The server (ttysnoops) is usually started
     by getty(8) or telnetd(8) and reads the file /etc/snooptab to find out which tty's should be cloned and which programs to run on them (usu-
     ally /bin/login). A tty may be snooped through a pre-determined (ie.  fixed) device, or through a dynamically allocated pseudo-tty (pty).
     This is also specified in the /etc/snooptab file. To connect to the pty, the client ttysnoop should be used. The available pseudo terminals
     pty are present as sockets in the directory /var/spool/ttysnoop/.

   Format of /etc/snooptab
     The /etc/snooptab file may contain comment lines (starting with a '#'), empty lines, or entries for tty's that should be snooped upon. The
     format of such an entry is as follows:

	   tty	 snoop-device	type   program

     where tty is the leaf-name of the tty that should be snooped upon (eg. ttyS2, not /dev/ttyS2) OR the wildcard '*', which matches ANY tty.
     snoop-device is the device through which tty should be snooped (eg. /dev/tty8) OR the literal constant "socket". The latter is used to tell
     ttysnoops that the snoop-device will be a dynamically allocated pty.  type specifies the type of program that should be run, currently recog-
     nized types are "init", "user" and "login" although the former two aren't really needed. Finally, program is the full pathname to the program
     to run when ttysnoops has cloned tty onto snoop-device.

EXAMPLE

     The following example /etc/snooptab file should illustrate the typical use of ttysnoop / ttysnoops:

	    #
	    # example /etc/snooptab
	    #
	    ttyS0    /dev/tty7	  login    /bin/login
	    ttyS1    /dev/tty8	  login    /bin/login
	    #
	    # the wildcard tty should always be the last one in the file
	    #
	    *	     socket	  login    /bin/login
	    #
	    # example end
	    #

     With the above example, whenever a user logs in on /dev/ttyS0 or /dev/ttyS1, either tty will be snooped through /dev/tty7 or /dev/tty8
     respectively. Any other tty's will be snooped through a pty that will be allocated at the time of login. The system-administrator can then
     run ttysnoop pty to snoop through the pty. Note that it is up to the system-administrator to setup getty and/or telnetd so that they execute
     ttysnoops instead of /bin/login.

SEE ALSO

     getty(8), telnetd(8)

FILES

     /etc/snooptab

BUGS

     The program is unable to do any terminal control-code translations for the original tty and the snoop-device. I doubt it will ever do this.

AUTHOR

     Carl Declerck, carl@miskatonic.inbe.net

BSD
								   August 8 1994							       BSD