Just an update here, I've been running around like an idiot for the past two and a bit days - having loads of attempts on web servers in particular. But have even had specific attacks on our firwall and other outward facing kit.
There have been attempts on our switches and routers, this is the most disaterous bug I can remember other than the version of Solaris 10 with "terry" the developers back door in the final release.
I have logs full of stuff like below - I've changed some of the stuff but you'll get the idea.
Regards
Dave
These 2 Users Gave Thanks to gull04 For This Post:
Hi everyone, first post here so please be gentle :-)
I normally likle to script in Bourne Shell simply for guarenteed compatibility across any system I might run across but this latest problem has me stumped.
Arrays is a rather significant construct missing from sh and after finding a way to... (2 Replies)
Hi guys !!
well i'm still new in learning UNIX , and actually i'm still studying it by myself ..
anyway, some people told me the Bourne-again shell is a good version of UNIX to work on , and i tried to download yesterday but i didn't know how to start it ...... the ReadMe file associated with... (3 Replies)
Hi,
I have a script that uses "nohup" command to execute a korn shell script. Which one is the correct shell to use bourne shell or korn shell to execute a korn shell? and why?
Thanks in advanced. (2 Replies)
Hi Guys,
My first post and simple one at that .. Really rusty with this shell scripting..\
I have a script called .. j.sh
I am calling
> j.sh LOG_PATH $BLMBRGDATA/blmbrg.properties
where j.sh is grep $1 $2 | cut -d',' -f2 .
$BLMBRGDATA is set to a directory path.
why do i get :-
$... (3 Replies)
I do not claim to be an expert, but I have done things with scripts that whole teams of folks have said can not be done. Of course they should have said we do not have the intestinal fortitude to git-r-done.
I have been using UNIX actually HPUX since 1992. Unfortunately my old computer died and... (7 Replies)
Hi All
I have writing a Korn Shell script to execute it on many of our servers. But some servers don't have Korn Shell installed, they use Borne Shell.
Some operations like calculation don't work :
cat ${file1} | tail -$((${num1}-${num2})) > ${file2}
Is it possible to activate Korn Shell... (3 Replies)
Hi,
The problem I have is that I want to create a list of folders whose names are read from a text file but the file names are in decimal. Each letter consists of an octet and the end of the folder name is defined by the white space character (0032)
For example, we have in the text... (2 Replies)
Attempting to write a script to eventually notify me via email for when there is packetloss across the backbone. I am looking for values greater than 0% in the mtr field.
#!/bin/sh
target=www.google.com
date +"%D"_"%T" >> /home/rich/mtr.log
echo "----------------------------------------" >>... (1 Reply)
Exercise Five
Write a Bourne shell script which:
• Professionalism: plan for this from the start.
• Has one command line argument.
• If the command line argument is a directory then the script should output the number of
files in the directory.
• If the command line argument is an ordinary... (2 Replies)
Could some one tell me the difference btw Bourne shell and the Kshell? Which is more flexible and reliable in terms of portability and efficiency. When i type the following command ..
$ echo $SHELL
yields me
/bin/sh
Does this tells me that I am in Bourne shell. If yes, how can i get... (6 Replies)
Discussion started by: bobby1015
6 Replies
LEARN ABOUT OSF1
sh
sh(1) General Commands Manual sh(1)NAME
sh - Shell, the standard command language interpreter
DESCRIPTION
[Tru64 UNIX] Tru64 UNIX provides two command interpreters with the name sh. The XCU5.0 and POSIX.2 compliant command interpreter sh is
available in the file /usr/bin/posix/sh and is described in the sh(1p) reference page. The Bourne shell, historically known as sh, is
available in the file /usr/bin/sh and is described in the sh(1b) reference page.
[Tru64 UNIX] Your initial, or login, shell is determined by your entry in the file /etc/passwd. This file can be changed only by your sys-
tem administrator. You must use whatever procedures are in place at your location to have this entry changed.
[Tru64 UNIX] If available on your system, you may use the passwd -s or the chsh commands to change your login shell.
Note
This option is not available if your site manages passwords through the Network Information Service (NIS) facility. Check with your system
administrator.
[Tru64 UNIX] Subsequent shells spawned from the initial shell depend on the value in the environment variable BIN_SH. If this variable is
set to xpg4, the POSIX shell is started. If this variable is set to svr4, an SVR4 compliant version of the shell is started. If this vari-
able is unset, the Bourne shell is started. If this variable is set to any other value, an error is reported and the results are unpre-
dictable. See the EXAMPLES section for information on setting this variable.
NOTES
[Tru64 UNIX] With Tru64 UNIX Version 4.0 the Korn shell, /usr/bin/ksh is the same as the POSIX shell /usr/bin/posix/sh.
RESTRICTIONS
[Tru64 UNIX] The file /etc/shells must include entries for both the POSIX shell /usr/bin/posix/sh and the Bourne shell, /usr/bin/sh. If
this file is incorrect, see your system administrator.
EXAMPLES
Using the Bourne, Korn, or POSIX shell, to set the variable BIN_SH to use the POSIX/ XCU5.0compliant shell, enter: BIN_SH=xpg4 export
BIN_SH Using the Bourne, Korn, or POSIX shell, to set the variable BIN_SH to use the SVR4 compliant shell, enter: BIN_SH=svr4 export BIN_SH
Using the Bourne, Korn, or POSIX shell, to unset the variable BIN_SH, enter: unset BIN_SH Using the C/ shell, to set the variable BIN_SH to
use the POSIX/XCU5.0 compliant shell, enter: setenv BIN_SH xpg4 Using the C/ shell, to set the variable BIN_SH to use the SVR4 compliant
shell, enter: setenv BIN_SH svr4 Using the C/ shell, to unset the variable BIN_SH, enter: unsetenv BIN_SH
FILES
User profile. Contains user information, including the login shell name. Contains the names of available and permitted shells.
SEE ALSO
Commands: csh(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), passwd(1)
Files: passwd(4), shells(4)
Standards: standards(5)sh(1)