Sponsored Content
Full Discussion: Ssh on ping result?
Top Forums Shell Programming and Scripting Ssh on ping result? Post 303026481 by MuntyScrunt on Wednesday 28th of November 2018 02:13:21 PM
Old 11-28-2018
Thanks folks. Some of this made it into the script and it works perfectly.

There is one outstanding issue which I can't find a way around. I thought it would be great if the ssh session could open with sudo su, it's not a work network, and also changing directory to where I do most of my work.

After blooming hours of trying all sorts of different things I got the sudo working, but concatenating another command gets ignored.

Obviously I'm opening another shell and any commands still in the original script aren't going to get to the new shell, what I don't understand is I can send a command with ssh, but I can't send two, I just can't see any bash reason why it wouldn't work.

Code:
sh="ssh -t"
command="user@192.168.xxx.xxx"
sud="sudo su"
run="$sh $command $sud"
exec $run

This works great, but it would be even better if after the sudo I could be dumped into a directory that I use a lot. But;
sud="sudo su; cd /usr/folder/folder"
Doesn't work. The sudo runs ok but the cd is ignored.

I'm trying to understand why. As I said I know I'm opening another shell and the script can't communicate with it directly, but if sudo su works why does the cd go missing?

Thanks again everyone, nothing here is work related or that important, but I'm enjoying the learning bit!!
 

10 More Discussions You Might Find Interesting

1. Linux

Can't SSH / ping Linux box !!!

I have a linux box build11 which can be pinged from build18 (Windows) box. And we can only login to the box (using SSH) from build18 box. Plz help to characterize the problem, network, DNS, DHCP, etc (or whatever which I am unsure) Any idea what may be the reason ? :confused: Thanks in... (4 Replies)
Discussion started by: csaha
4 Replies

2. Shell Programming and Scripting

Problem storing SSH result in a variable

i have this SSH command which runs perfectly on command prompt in sunOS ssh -o Port=${portno} ${uname}@${server} find ${dir_path} -name '***' output : /usr/local/home/*** My problem is when i run same command in my script #!/usr/bin/ksh res=`ssh -o Port=${portno} ${uname}@${server}... (1 Reply)
Discussion started by: prash184u
1 Replies

3. Solaris

could not ssh and ping

hi , i cannot ssh to a server , i have restarted the ssh instances also. and i cannot ping to the server.. any ideas ..plz (5 Replies)
Discussion started by: jegaraman
5 Replies

4. Solaris

could not ssh and ping

Hi, I have a solaris 8 machine. I see ssh is running in the machine sbnismwp2# ps -aef | grep ssh root 947 945 0 04:34:45 ? 0:00 /export/opt/SSHtecagt/sbin/ssh-mgmt-sysmonitor root 945 1 0 04:34:45 ? 0:00 /export/opt/SSHtecagt/sbin/ssh-mgmt-agent... (11 Replies)
Discussion started by: jegaraman
11 Replies

5. Shell Programming and Scripting

prevent ssh from executing result in shell

Hi, I am writing a script on Solaris 10 and want to execute a remote ssh command. Normally this command should just return the value 0000000000002356 but when using ssh it seems it is passing the result to the shell to execute. ssh root@10.5.112.145 `/usr/bin/nawk -F\, '$1=="USG" && $2=="01"... (3 Replies)
Discussion started by: borderblaster
3 Replies

6. Solaris

Ping = no, SSH = eventually. Next step?

I have a Solaris 9 server that does not return a ping. When I try to log in via SSH I eventually get in. I am logged in now. I know this is a wide open question, but can you recommend some things I should check? . Thanks in advance, ~R (2 Replies)
Discussion started by: abstractrick
2 Replies

7. Shell Programming and Scripting

Perl : code on ping showing difference result

Hi all, I am using the below code to ping a code and print whehter the connection is successful or not. use Net::Ping; $p = Net::Ping->new(); my $host = "x.x.x.x"; # print "$host is alive.\n" if $p->ping($host); if ($p->ping($host,3)) { print... (0 Replies)
Discussion started by: scriptscript
0 Replies

8. Shell Programming and Scripting

Ping result talking too long

Hello all, I am writing a script that pings various machines to check connectivity. If a machine is available, the prompt returns a result immediately: root@ops # ping 172.21.5.5 172.21.5.5 is alive BUT if a machine is Down , the reply takes a long time to come. The issue is I want to... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies

9. AIX

Not able to ssh or ping a server

Hi, Earlier I was able to ssh /ping the server but now it just hangs Please suggest how to troubleshoot. Best regards, Vishal (4 Replies)
Discussion started by: Vishal_dba
4 Replies

10. UNIX for Advanced & Expert Users

Cant ssh, but ping works

I cant ping to some of my machines, but ping works. I attach screenshots. Port is open and it is 22. I can't figure out why i cant access. https://www.unix.com/attachments/unix-for-advanced-and-expert-users/7492d1541541072-cant-ssh-but-ping-works-sshlisten-jpg... (17 Replies)
Discussion started by: tomislav91
17 Replies
SUDOREPLAY(8)						       MAINTENANCE COMMANDS						     SUDOREPLAY(8)

NAME
sudoreplay - replay sudo session logs SYNOPSIS
sudoreplay [-d directory] [-f filter] [-m max_wait] [-s speed_factor] ID sudoreplay [-d directory] -l [search expression] DESCRIPTION
sudoreplay plays back or lists the session logs created by sudo. When replaying, sudoreplay can play the session back in real-time, or the playback speed may be adjusted (faster or slower) based on the command line options. The ID should be a six character sequence of digits and upper case letters, e.g. 0100A5, which is logged by sudo when a command is run with session logging enabled. In list mode, sudoreplay can be used to find the ID of a session based on a number of criteria such as the user, tty or command run. In replay mode, if the standard output has not been redirected, sudoreplay will act on the following keys: ' ' (space) Pause output; press any key to resume. '<' Reduce the playback speed by one half. '>' Double the playback speed. OPTIONS
sudoreplay accepts the following command line options: -d directory Use directory to for the session logs instead of the default, /var/log/sudo-io. -f filter By default, sudoreplay will play back the command's standard output, standard error and tty output. The -f option can be used to select which of these to output. The filter argument is a comma-separated list, consisting of one or more of following: stdout, stderr, and ttyout. -l Enable "list mode". In this mode, sudoreplay will list available session IDs. If a search expression is specified, it will be used to restrict the IDs that are displayed. An expression is composed of the following predicates: command command pattern Evaluates to true if the command run matches command pattern. On systems with POSIX regular expression support, the pattern may be an extended regular expression. On systems without POSIX regular expression support, a simple substring match is performed instead. cwd directory Evaluates to true if the command was run with the specified current working directory. fromdate date Evaluates to true if the command was run on or after date. See "Date and time format" for a description of supported date and time formats. group runas_group Evaluates to true if the command was run with the specified runas_group. Note that unless a runas_group was explicitly specified when sudo was run this field will be empty in the log. runas runas_user Evaluates to true if the command was run as the specified runas_user. Note that sudo runs commands as user root by default. todate date Evaluates to true if the command was run on or prior to date. See "Date and time format" for a description of supported date and time formats. tty tty Evaluates to true if the command was run on the specified terminal device. The tty should be specified without the /dev/ prefix, e.g. tty01 instead of /dev/tty01. user user name Evaluates to true if the ID matches a command run by user name. Predicates may be abbreviated to the shortest unique string (currently all predicates may be shortened to a single character). Predicates may be combined using and, or and ! operators as well as '(' and ')' for grouping (note that parentheses must generally be escaped from the shell). The and operator is optional, adjacent predicates have an implied and unless separated by an or. -m max_wait Specify an upper bound on how long to wait between key presses or output data. By default, sudo_replay will accurately reproduce the delays between key presses or program output. However, this can be tedious when the session includes long pauses. When the -m option is specified, sudoreplay will limit these pauses to at most max_wait seconds. The value may be specified as a floating point number, .e.g. 2.5. -s speed_factor This option causes sudoreplay to adjust the number of seconds it will wait between key presses or program output. This can be used to slow down or speed up the display. For example, a speed_factor of 2 would make the output twice as fast whereas a speed_factor of <.5> would make the output twice as slow. -V The -V (version) option causes sudoreplay to print its version number and exit. Date and time format The time and date may be specified multiple ways, common formats include: HH:MM:SS am MM/DD/CCYY timezone 24 hour time may be used in place of am/pm. HH:MM:SS am Month, Day Year timezone 24 hour time may be used in place of am/pm, and month and day names may be abbreviated. Note that month and day of the week names must be specified in English. CCYY-MM-DD HH:MM:SS ISO time format DD Month CCYY HH:MM:SS The month name may be abbreviated. Either time or date may be omitted, the am/pm and timezone are optional. If no date is specified, the current day is assumed; if no time is specified, the first second of the specified date is used. The less significant parts of both time and date may also be omitted, in which case zero is assumed. For example, the following are all valid: The following are all valid time and date specifications: now The current time and date. tomorrow Exactly one day from now. yesterday 24 hours ago. 2 hours ago 2 hours ago. next Friday The first second of the next Friday. this week The current time but the first day of the coming week. a fortnight ago The current time but 14 days ago. 10:01 am 9/17/2009 10:01 am, September 17, 2009. 10:01 am 10:01 am on the current day. 10 10:00 am on the current day. 9/17/2009 00:00 am, September 17, 2009. 10:01 am Sep 17, 2009 10:01 am, September 17, 2009. FILES
/var/log/sudo-io The default I/O log directory. /var/log/sudo-io/00/00/01/log Example session log info. /var/log/sudo-io/00/00/01/stdin Example session standard input log. /var/log/sudo-io/00/00/01/stdout Example session standard output log. /var/log/sudo-io/00/00/01/stderr Example session standard error log. /var/log/sudo-io/00/00/01/ttyin Example session tty input file. /var/log/sudo-io/00/00/01/ttyout Example session tty output file. /var/log/sudo-io/00/00/01/timing Example session timing file. Note that the stdin, stdout and stderr files will be empty unless sudo was used as part of a pipeline for a particular command. EXAMPLES
List sessions run by user millert: sudoreplay -l user millert List sessions run by user bob with a command containing the string vi: sudoreplay -l user bob command vi List sessions run by user jeff that match a regular expression: sudoreplay -l user jeff command '/bin/[a-z]*sh' List sessions run by jeff or bob on the console: sudoreplay -l ( user jeff or user bob ) tty console SEE ALSO
sudo(8), script(1) AUTHOR
Todd C. Miller BUGS
If you feel you have found a bug in sudoreplay, please submit a bug report at http://www.sudo.ws/sudo/bugs/ SUPPORT
Limited free support is available via the sudo-users mailing list, see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or search the archives. DISCLAIMER
sudoreplay is provided ``AS IS'' and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. See the LICENSE file distributed with sudo or http://www.sudo.ws/sudo/license.html for complete details. 1.7.4 July 12, 2010 SUDOREPLAY(8)
All times are GMT -4. The time now is 05:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy