09-09-2008
Noop....basically that's how UNIX works, you never know what's going on behind the scene.
BASEDIR is a default environment variable. It represents where the root install path, based on Sun document and my understanding.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I have this code, and i want work with a ls -shalR output in .txt
What i need read to do this??
Where start?
#!/usr/bin/perl
# Allrights- A perl tool for making backups of file permissions
# Copyright (C) 2005 Norbert Klein <norbert@acodedb.com>
# This program is free... (1 Reply)
Discussion started by: joangopan
1 Replies
2. Shell Programming and Scripting
I am posting a script below which essentially excutes the following functions in the described order.
1) From a source directory pools together three files generated by system logs for each user session, tar's these files and archives them as a log set in a destination directory and these... (0 Replies)
Discussion started by: Sammy
0 Replies
3. UNIX for Advanced & Expert Users
I am creating a package(Solaris10 on sparc) that needs user input.
As I understand it, I need to use a request script.
My problem is that the value I set in my request script is not visible in my postinstall script. Not sure if I am doing it right.
Here is an example request script... (4 Replies)
Discussion started by: Tornado
4 Replies
4. Shell Programming and Scripting
Hi,
I have a script which connect to ATM's and pull two files from the ATM.
The which i try to pull is like
PIC20085200001*.JPG
First 7 digit consist of year montn and date as well
After todays execution i want to change the date to next date
I add few lines in the script but it is not... (6 Replies)
Discussion started by: Renjesh
6 Replies
5. Shell Programming and Scripting
Is there an equivalent of basedir in shell script? I have a file location and I want to lowercase just the filename not the path. (2 Replies)
Discussion started by: mainegate
2 Replies
6. Shell Programming and Scripting
Hi,
In the request script I need to read user input and store to variable to use it later in postinstall script.
e.g.
LOGDIR=/app/log
echo "Please type the Log Directory : (current value: $LOGDIR)"
read LOGDIR
When asked, if the user enters a value the parameter is ok and I... (2 Replies)
Discussion started by: potro
2 Replies
7. Shell Programming and Scripting
hello forum members,
I have a script which is used find the Uname and passwords and redirects into a output.txt file.I hardcoded a string "ciadev" but iwant search two more strings also "absdev" and "absprod" So modify this script please.
I am lookinmg forward from you,
please find the below... (2 Replies)
Discussion started by: rajkumar_g
2 Replies
8. Shell Programming and Scripting
I am working on a script to install a software distribution which ships as a *.tar.gz file. The company doesn't name the dist consistently, but the resulting directory out of the *.tar.gz file (ie: XXX_X_X_X) is consistent and shows the software version.
I'm writing this with BASH-3.25.x... (4 Replies)
Discussion started by: forrie
4 Replies
9. Shell Programming and Scripting
Hello;
I'm having about 800 log files and i'm trying to write a script that report the counts of lines per second or "requests per second" in each log file and report the output which includes the timestamp for the highest lines per second count and the log file name and the highest number per... (5 Replies)
Discussion started by: Katkota
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)