03-21-2013
777 is not the magic sledgehammer to fix all permissions problems. It's certainly not a habit I want to teach to kids. 660, or even 600, should do(executable permission is not needed for a script you source). Or just leave it alone.
The traditional location for user config files is ${HOME}, aka ~/, more appropriate than /tmp/
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am stuck while developing a shell sub-routine which checks the log file for "success" or "failure". The subroutine reads the log file and checks for key word "success", if found it set the variable (found=1). It returns success or failure based on this variable.
My problem is, I can... (2 Replies)
Discussion started by: cjjoy
2 Replies
2. Shell Programming and Scripting
Hi,
I am new to unix and using linux 7.2. I would like to create a script that would make it easyer for me to run my java programms. At the moment I have to type java myJavaprogram
I am trying to write a script that will allow me to type something like this "myscript myJavaprogram" or maybe... (4 Replies)
Discussion started by: cmitulescu
4 Replies
3. Shell Programming and Scripting
hi all,
i'm using the following script,
Status=1
Function_do ()
{
while read line;
do
if ; then
#echo $line
if ; then
Status=0
echo " LINKINK ERROR "
fi
fi
done < ldd.log
}
Function_do (4 Replies)
Discussion started by: vij_krr
4 Replies
4. Shell Programming and Scripting
Hi All,
I would like to develop a shell script for stop & start an application server (1-4) on Solaris box. Here are the user requirements for this task.
1. User will input the option which server they wish to stop.
2. Will clear cache files from specific location.
3. ... (1 Reply)
Discussion started by: venga
1 Replies
5. What is on Your Mind?
Hi all,
I want to know what is the scope and job status of shell Programming and scripting. Does it have any attractive jobs? (2 Replies)
Discussion started by: malikshahid85
2 Replies
6. Shell Programming and Scripting
The scope of the shell/perl script is to read the input text file. Validate the expiry date of each certificate and send the mail to the user. The user takes action to add the new certificate to the storage file and user owns the responsibility to update the input text file with the new certificate... (5 Replies)
Discussion started by: casmo
5 Replies
7. UNIX for Dummies Questions & Answers
Hi,
Pleasse could someone advise why i'm getting this error below - No such file or directory
dev6:$ ls -ltr ReleaseManagement.sh
-rwxr-xr-x 1 dev fix 4830 Aug 22 11:13 ReleaseManagement.sh
dev6:$ ./ReleaseManagement.sh
: No such file or directory
dev6:$
thank you (2 Replies)
Discussion started by: venhart
2 Replies
8. OS X (Apple)
This site is the first to get this snippet.
It will capture an audio recording of any time length within the limits of OSX's QuickTime Player's capablility...
A shell script derivative of this will be used as a further capture for CygWin's AudioScope.sh.
Thoroughly read ALL the comments in... (0 Replies)
Discussion started by: wisecracker
0 Replies
9. Shell Programming and Scripting
Hi,
I want 10000+ unique Audio file of approx 2MB each. How can i generate numerous audio files using shell script. Any tool, command or suggestions are welcome.
If i give one audio seed file then can we create numerous unique files with same seed file?
Any help is highly appreciable.... (11 Replies)
Discussion started by: sushil.kumar
11 Replies
10. OS X (Apple)
Hi all...
Well I have not been inactive but working out how to make OSX 10.14.x command line audio player have a variable sample rate.
This is a back door as afplay does not have a sample rate flag unlike aplay for ALSA, in Linux flavours.
This is a DEMO only but a derivative of it will... (2 Replies)
Discussion started by: wisecracker
2 Replies
LEARN ABOUT SUSE
inncheck
INNCHECK(8) System Manager's Manual INNCHECK(8)
NAME
inncheck - check inn configuration and database files.
SYNOPSIS
inncheck [ -a ] [ -v ] [ -pedantic ] [ -f ] [ -perm ] [ -noperm ] [ file=value | file ]
DESCRIPTION
Inncheck examines various configuration files and databases and verifies things about them. Things verified depend on the file being
checked, but generally are things like permissions, ownership, syntax errors in config files, etc.
Inncheck does not make changes to any files -- it just reports what it thinks may be wrong, and it is up to the operator to fix the prob-
lem.
The set of files checked may be restricted by using file or file=value arguments. For example, putting incoming.conf causes only the incom-
ing.conf file to be checked. Using incoming.conf=/tmp/incoming.conf on the command line will cause inncheck to only verify the incom-
ing.conf file, and it will perform the checks on the file /tmp/incoming.conf file instead of the default one.
Valid values for file are:
active
control.ctl
expire.ctl
incoming.conf
inn.conf
moderators
newsfeeds
nntpsend.ctl
passwd.nntp
readers.conf
OPTIONS
-a If any ``file'' value or ``file=value'' pairs (see below) are given, then normally only the files they refer to are checked. Use the
``-a'' flag to specify that all files should be checked regardless. In this case the form file=value will be the more useful.
-v Use the ``-v'' option to get more verbose output.
-pedantic
Use the ``-pedantic'' option to get reports on things that are not necessarily wrong, but may indicate a bad configuration -- such
as inn.conf missing a key.
-f Use the ``-f'' flag to have inncheck print the appropriate chown/chgrp/chmod command necessary to fix a problem that it reports.
Any other output lines will be prefixed with a ``#'' character to make the output be valid input for a shell. Note that the
``-perm'' flag must be used as well when using this flag.
-perm Inncheck checks all files for permission problems. If the ``-perm'' flag is used, then only the files specified by the file or
file=value command line arguments will be checked for problems other than permission problems.
-noperm
To avoid doing any checking of file permissions or ownership, use the ``-noperm'' option.
EXAMPLES
To have inncheck check all files for syntax and permission problems simply:
inncheck
To have inncheck check all files for permission problems and to verify the syntax of the active and incoming.conf files do:
inncheck -perm active incoming.conf
To fix the permissions problems noted in the output of the above command, modify it as follow:
inncheck -f -perm | sh
To have inncheck check the test newsfeeds file in /var/tmp/newsfeeds.testing, do:
inncheck newsfeeds=/var/tmp/newsfeeds.testing
To have inncheck check all the files as it normally does, but to specify a different location for the newsfeeds file, so:
inncheck -a newsfeeds=/var/tmp/newsfeeds.testing
BUGS
If the ``-f'' and ``-perm'' options are used together, along with ``-a'' or some ``file'' or ``file=value'' arguments that refer to a file
with a syntax problem, then the output will no longer be valid input for a shell.
HISTORY
Written by Brendan Kehoe <brendan@cygnus.com> and Rich Salz <rsalz@uunet.uu.net> This is revision 8409, dated 2009-04-11.
SEE ALSO
active(5), expire.ctl(5), history(5), incoming.conf(5), inn.conf(5), newsfeeds(5)
INNCHECK(8)