09-23-2013
Automating Linux Script
I want to automate the creation or processing of the following:
- Directory and subdirectory creation for your scenario company
- Files in each of the directories
- Symbolic links from 2 subdirectories to their parent directories
- Setting appropriate file permissions for the directories and files:
- Directories
- the file owner can read, modify and access the scenario company directories,
- the group members can read and access the scenario company directories,
- everyone else has no access.
- Files
- The owner can read and modify the file,
- the group members can only read the file
- everyone else has no permissions at all.
- Include branching to only execute the directory, file and link commands only if the directory or file does not already exist.
- Set up an error log file with commands to route the errors messages into it.
However, I have only been using Linux for a few weeks now and this is proving to be extremely complicated. I have read tutorials on automating but cannot understand it. This is a school assignment due today by 11:59pm central time. Ant assistance would be greatly appreciated!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have to write an automated sftp script which uses password authentication method to access the remote server. I want to pass the password as a parameter or to be included in the script itself, so that when i run the sftp script, it should not prompt me to enter the password.
Thanks in advance... (1 Reply)
Discussion started by: Rajeshsu
1 Replies
2. Shell Programming and Scripting
Hi all
I am trying to create a script to automate the creating of filesystems.
The problem I am having is as follows:-
After creating the Log Logical Volume, I want to format it, using the logform command.
The Logform command expects user intervention, by typing 'y' and 'enter' to continue.... (2 Replies)
Discussion started by: TheDoc
2 Replies
3. UNIX for Dummies Questions & Answers
Hi all.
basically i need to run a script every 30 minutes.
my script is simply an error report:
errpt
thats it, is there anyway to make this happen every 30 minutes
without having to type errpt in, the script will get bigger as i add more things to do but just need to know how to... (8 Replies)
Discussion started by: hassanj
8 Replies
4. Shell Programming and Scripting
I need to run a command at the end of a backup job and this command will produce a report of what my backup jobs have collected in the previous day. The real problem is that this binary works with absolute dates only, so I should have to modify the script every single time I need it to work. It... (1 Reply)
Discussion started by: italia1971luca
1 Replies
5. Shell Programming and Scripting
I have a script that will install software on all remote host. At the end of the script it starts the install.sh part and goes into a interactive mode asking Yes or No questions and prompting to add a username and password. My question is how can I script this so that these questions are... (7 Replies)
Discussion started by: soupbone38
7 Replies
6. Shell Programming and Scripting
Dear Scripting Gods
I've never done shell scripting before and have only recently got to grips with Perl, so apologies for my naivity. I've written a perl program which takes in two files as arguments (these are text documents which take in the information I need) The perl program spits out a... (1 Reply)
Discussion started by: fraizerangus
1 Replies
7. Shell Programming and Scripting
Hi Guys,
There are some emails going deferred as we got some new IP's from our ISP. So I was trying to manually copy the deferred mail and forward it to our sales team so that they can contact our client. I am new to this script thing, but luckily I was able to write the code to extract the data... (1 Reply)
Discussion started by: linuxrulz
1 Replies
8. Shell Programming and Scripting
Hi,
I have a perl script that takes in 2 numerical values as ARGV.
perl script.pl parameter1 num1 num2
in my case I have 1000's of num1 and num2. I can have them in separate files. Please let me know how to automate this run using shell scripting or using awk, so that I don't have to... (4 Replies)
Discussion started by: Lucky Ali
4 Replies
9. Shell Programming and Scripting
is it possible to automate crontab through script... I ll be getting the data i.e. cron entries from DB. (5 Replies)
Discussion started by: nikhil jain
5 Replies
10. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
I want to automate the creation or processing of the following:
Directory and subdirectory creation for your scenario company
Files in each of the directories
Symbolic links from 2 subdirectories to their parent directories... (16 Replies)
Discussion started by: ekglag2
16 Replies
LEARN ABOUT HPUX
packingrules
packingrules(4) Kernel Interfaces Manual packingrules(4)
NAME
packingrules - packing rules file for cachefs
DESCRIPTION
is a packing rules file for packingrules contains a list of directories and files that are to be packed. It also contains a list of direc-
tories and files that are to be specifically excluded from packing. See cachefspack(1M).
Many users choose to manually create the packing rules file and edit it by hand. Users can edit the packingrules (using any editor) to
permanently change the packingrules file, or to gain access to more powerful options that are not available from the command line (such as
the command). It is much easier to enter complex wildcard expressions by editing the packingrules file.
Following is a description of the lines in a packing rules file. Blank lines and lines that begin with a pound sign are ignored. Lines
can be continued by placing a backslash () immediately before the newline character. All other lines in the packingrules file have one
of the following formats:
This line identifies a directory (or pair of directories)
under which files should be packed. At least one directory name must be specified. The arguments must be fully qualified
path names and may include environment variables.
This line enumerates a list of files and subdirectories
beneath the current directory to be packed. This specification is recursive. That is, specifying the name of a directory
automatically includes all files and subdirectories it contains.
This line enumerates a list of files that are not to be packed.
Regular expressions are permitted.
There are important differences between the arguments to the and the statements. The arguments to statements can contain slashes and are
interpreted as file names relative to the directories. The arguments to statements are simpler names or expressions that cannot contain
slashes. An statement will not override a LIST statement. statements only exclude files that are found beneath listed directories.
If the first name argument to a or an statement begins with an exclamation point the remainder of the statement will be executed as a com-
mand that will be run in the current directory. The output of the command will be treated as a list of newline separated file names to be
packed command) or to be excluded from the packing list command). For the command, the resulting file names will be interpreted relative
to the enclosing directory.
Blanks can be embedded in an argument by escaping them with a backslash () or enclosing the argument in double quotes (` " '). Double
quotes can be passed in arguments by escaping the double quotes with a backslash ().
lines only apply to the statement that precedes them. lines can appear before any statement (in which case they apply to all or after a
statement (in which case they only apply to the that precedes them). Any number of these statements can occur in any combinations. The
order is not important.
EXAMPLES
The use of these statements is illustrated in the following packing rules file.
#
# Ignore junk files.
#
IGNORE core *.o *.bak *%
#
# Pack everything in the work subdirectory and in a few
# favorite mailboxes.
#
BASE /net/bigserver/export/home/myname
LIST work
LIST m/incoming
LIST m/action
LIST m/pending
#
# Pack two important project directories but skip
# all postscript output.
#
BASE /net/bigserver/export/projects $HOME/projects
LIST poindexter epiphany
IGNORE *.ps
#
# Pack the foonly package.
#
BASE /net/bigserver/opt/foonly /opt/foonly
LIST !cat .packinglist
#
# Also pack the latest executables for the standard
# build environment.
#
BASE /net/bigserver/export/buildenv $HOME/buildenv
LIST !find . -type f -a -perm -111 -a -print
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
cachefspack(1M).
packingrules(4)