05-05-2006
As much as I like your answer Deepsoul...
It's simple - to do a script you have a choice of shells or languages - choose one that you are use to using (such as the shell you use normally - do a
echo $SHELL to find out what you are using).
Once you have that, cd to your home directory - vi a new file (such as my-new-script)
$ cd
$ vi my-new-script
Insert the commands in the same order you would run them normally from the command line - only difference - add #!/bin/sh or whatever shell you are using at the top - this lets the system know what you are running these commands under
#!/bin/sh
/bin/cp /dirA/* /dirB/*
exit
Then use chmod as suggested to change the script to executable
A script is putting all the commands you usually have to do into a file to run - it's doing what you would do automatically (via cron if needed). The only thing a script does it make it so you don't have to type those commands every time.
Try this on your system:
$ cd
$ vi hbo
i
#!/bin/sh
date +'%n %D %A %T%n'
exit
Hit the escape key, put in a wq to write-quit from the vi editor
$ chmod 744 hbo
$ ./hbo
01/18/05 Tuesday 19:44:04
$
That's all there is to it -
7 More Discussions You Might Find Interesting
1. Programming
Now that I have getch() to work, I have yet another problem. BTW, thank you for answering these questions, I do ask a lot, only because I am eager to know, what is a board used for anyways :)
Ok, he's the problem...
#include iostream.h
#include conio.h
int main()
{
char movement;
... (2 Replies)
Discussion started by: mbolthouse
2 Replies
2. Solaris
Im trying to edit a 113 meg file in VI and i get the error TMP FILE TOO LARGE.
Does someone know how to get around this?
Thanks! (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
3. UNIX for Dummies Questions & Answers
Hello
if I like to move file from defined directories system to new directory that not contained any directories system structure .
But I like to create the same file system structure as source directory for example :
I have 2 directories: foo1 and foo2
foo1 have directories and foo2 have... (2 Replies)
Discussion started by: umen
2 Replies
4. UNIX for Dummies Questions & Answers
hallo, ik heb hier een vraagje. hoeveel gebruikers kunnen er op 1 unix systeem. hopelijk antwoorden golle nu want ik moet da vinde voor school en die leerkracht zaagt. :p
groetjes eu wacht wa was mijne nick ah ja vraagje
groetjes vraagje
ik kan geen engels dus antwoord liever in het... (1 Reply)
Discussion started by: vraagje
1 Replies
5. Shell Programming and Scripting
Hey my friend was asking me if i knew a way to cout how many different words in a file. I told him no not off hand, but i was thinking about it, and i started to wonder also. I imagine this is probably pretty simple im just missing something, I keep confusing my self with how you would compair and... (16 Replies)
Discussion started by: yodadbl07
16 Replies
6. Hardware
How to add 3 moniters to a pc set up? (2 Replies)
Discussion started by: clicstic
2 Replies
7. AIX
Hi,
Can anyone please explain a little about df command. I have following question:
Following example is showing % used as 4 where as total free blocks are 15.46 out of 16.00 MB blocks.
df -m /test
Filesystem MBblocks Free %Used Iused %Iused ... (5 Replies)
Discussion started by: itsabhi9
5 Replies
SETUID(1) General Commands Manual SETUID(1)
NAME
setuid - run a command with a different uid.
SYNOPSIS
setuid username|uid command [ args ]
DESCRIPTION
Setuid changes user id, then executes the specified command. Unlike some versions of su(1), this program doesn't ever ask for a password
when executed with effective uid=root. This program doesn't change the environment; it only changes the uid and then uses execvp() to find
the command in the path, and execute it. (If the command is a script, execvp() passes the command name to /bin/sh for processing.)
For example,
setuid some_user $SHELL
can be used to start a shell running as another user.
Setuid is useful inside scripts that are being run by a setuid-root user -- such as a script invoked with super, so that the script can
execute some commands using the uid of the original user, instead of root. This allows unsafe commands (such as editors and pagers) to be
used in a non-root mode inside a super script. For example, an operator with permission to modify a certain protected_file could use a
super command that simply does:
cp protected_file temp_file
setuid $ORIG_USER ${EDITOR:-/bin/vi} temp_file
cp temp_file protected_file
(Note: don't use this example directly. If the temp_file can somehow be replaced by another user, as might be the case if it's kept in a
temporary directory, there will be a race condition in the time between editing the temporary file and copying it back to the protected
file.)
AUTHOR
Will Deich
local SETUID(1)