04-15-2011
Quote:
Originally Posted by
Corona688
Which are what? For one reason or another, different profiles are being loaded when you login one way than another.
Try echo $SHELL ; echo $USER in both to make double-sure you're actually running bash, and as the same user.
You could run exec bash -l to make sure you're running in your preferred shell.
Everything is identical on both, shh log in as well as on machine which I log to by ThinLink.
I really thing that the problem is that I am logged to wrong server, because I have just find that there are three different types of servers and I need to be probably logged to application servers which I am apparently not when I am using shh. I have contacted support of the servers but it will take some time to get answer back. When I will get an answer I will post it here too, if it will solve the problem
Thank you very much for your help.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm new to unix and I have a fairly simple problem:
Lets say I am in a specific directory and I run the command: "dirs" ,
I get an output of all the folders that i pushed into the stack (as expected),
buut,
when when I create a script (called test):
#! /bin/csh
dirs
and then i run:... (2 Replies)
Discussion started by: owijust
2 Replies
2. Shell Programming and Scripting
I have written some scripts that do a few admin tasks on 23 servers I manage.
Usually I execute these scripts from one server by running ssh commands remotley, i.e.
ssh root@server2 shellscript, ssh root@server2 shellscript & so on..
It works fine but I want to improve this by writing a... (3 Replies)
Discussion started by: Moxy
3 Replies
3. Shell Programming and Scripting
I ran an ssh command to run a script on a remote server
ssh -l <user> <servername> /path/to/script/scriptname
This works fine - and the script is executed correctly.
However - I put this command into a script, that I want to run from cron every hour, to execute the file on the remote... (31 Replies)
Discussion started by: frustrated1
31 Replies
4. Shell Programming and Scripting
Executing two unix commads via perl script one after another
e.g: make clean
bsub -i -q short make
have tried using exec but the second command doesnt executes (1 Reply)
Discussion started by: rajroshan
1 Replies
5. Shell Programming and Scripting
Hi All,
Is there a way in which a long running command can terminate by itself inside a script? I need something like below:
echo Start
<command>
exit
If the <command> is taking more than say 100 seconds to complete, the script should exit without manual intervention.
Thanks,
Deepak (2 Replies)
Discussion started by: deepakgang
2 Replies
6. Shell Programming and Scripting
Hi all!
I am trying to write a script that will check if a certain directory is available at several different nodes and then do stuff in it .....
On the beginning of the script I give as a variable the directory and the number of the nodes and then I loop like this:
for... (3 Replies)
Discussion started by: idet2
3 Replies
7. Shell Programming and Scripting
I'm trying to copy files from a remote windows server to Unix server. I was successfully able to copy files from windows server using command prompt but when I run these commands from a script it's not working as expected. commands used:
sftp user@remoteserver.com
lcd local_dir
cd... (3 Replies)
Discussion started by: naresh7590
3 Replies
8. Shell Programming and Scripting
Hello,
I'm trying to create a ksh script to ssh to a remote server, enter the password and a couple commands. For security reasons I have changed the login, password and ip in my example.
#!/bin/ksh
ssh -t -t username@12.5.5.3 << EOF
password
cd bin
pwd
EOF
When I run it. It... (5 Replies)
Discussion started by: seekryts15
5 Replies
9. Shell Programming and Scripting
Hi All,
I have put a perl script together to go and collect some information from multiple nodes/endpoints. The script works absolutly fine however I want to make it quicker.
You will see in the below that my script calls an expect script called ssh_run_cmd2.exp followed by the IP of... (7 Replies)
Discussion started by: mutley2202
7 Replies
10. Shell Programming and Scripting
Hi,
I am trying to run commands on a list of servers that I can ssh to and just want to know if there is a 'cleaner' way of doing this.
At the moment, I am doing as below. Is there a way that I can escape the double quote differently? If a use a single quote to enclose the commands that I... (1 Reply)
Discussion started by: newbie_01
1 Replies
LEARN ABOUT SUNOS
nisping
nisping(1M) nisping(1M)
NAME
nisping - send ping to NIS+ servers
SYNOPSIS
/usr/lib/nis/nisping [-uf] [-H hostname] [-r | directory]
/usr/lib/nis/nisping -C [-a] [-H hostname] [directory]
In the first line, the nisping command sends a ``ping'' to all replicas of an NIS+ directory. Once a replica receives a ping, it will
check with the master server for the directory to get updates. Prior to pinging the replicas, this command attempts to determine the last
update "seen" by a replica and the last update logged by the master. If these two timestamps are the same, the ping is not sent. The -f
(force) option will override this feature.
Under normal circumstances, NIS+ replica servers get the new information from the master NIS+ server within a short time. Therefore, there
should not be any need to use nisping.
In the second line, the nisping -C command sends a checkpoint request to the servers. If no directory is specified, the home domain, as
returned by nisdefaults(1), is checkpointed. If all directories, served by a given server, have to be checkpointed, then use the -a option.
On receiving a checkpoint request, the servers would commit all the updates for the given directory from the table log files to the data-
base files. This command, if sent to the master server, will also send updates to the replicas if they are out of date. This option is
needed because the database log files for NIS+ are not automatically checkpointed. nisping should be used at frequent intervals (such as
once a day) to checkpoint the NIS+ database log files. This command can be added to the crontab(1) file. If the database log files are not
checkpointed, their sizes will continue to grow.
If the server specified by the -H option does not serve the directory, then no ping is sent.
Per-server and per-directory access restrictions may apply; see nisopaccess(1). nisping uses NIS_CPTIME and NIS_PING (resync (ping) of
replicas), or NIS_CHECKPOINT (for checkpoint). Since the NIS_PING operation does not return a status, the nisping command is typically
unable to indicate success or failure for resyncs.
-a Checkpoint all directories on the server.
-C Send a request to checkpoint, rather than a ping, to each server. The servers schedule to commit all the transactions to
stable storage.
-H hostname Only the host hostname is sent the ping, checked for an update time, or checkpointed.
-f Force a ping, even though the timestamps indicate there is no reason to do so. This option is useful for debugging.
-r This option can be used to update or get status about the root object from the root servers, especially when new root
replicas are added or deleted from the list.
If used without -u option, -r will send a ping request to the servers serving the root domain. When the replicas receive a
ping, they will update their root object if needed.
The -r option can be used with all other options except with the -C option; the root object need not be checkpointed.
-u Display the time of the last update; no servers are sent a ping.
-1 No servers were contacted, or the server specified by the -H switch could not be contacted.
0 Success.
1 Some, but not all, servers were successfully contacted.
Example 1: Using nisping
This example pings all replicas of the default domain:
example% nisping
Note that this example will not ping the org_dir and groups_dir subdirectories within this domain.
This example pings the server example which is a replica of the org_dir.foo.com. directory:
example% nisping -H example org_dir.foo.com.
This example checkpoints all servers of the org_dir.bar.com. directory.
example% nisping -C org_dir.bar.com.
NIS_PATH If this variable is set, and the NIS+ directory name is not fully qualified, each directory specified will be
searched until the directory is found.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
crontab(1), nisdefaults(1), nisopaccess(1), nislog(1M), nisfiles(4), attributes(5)
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
12 Dec 2001 nisping(1M)