I have some basic doubts. Can someone clarify in this forum?
1)if
then
eval ' tset -s -Q -m ':?hp' '
else
eval ' tset -s -Q '
what does it exactly mean in .profile?
2) what are 'nobody' and 'noaccess' usernames in /etc/passwd file.
... (3 Replies)
Hello all. Let me start off by saying I know a little more then it seems by me asking this question... here goes
I have an old 486 box and I want to start messing around with unix. I've been taking classes for 3 or 4 years in c programming in unix, so I am used to the commands and such, but I... (1 Reply)
Could someone tell me the command to find out the OS version which will give 12 character not the 9 characters(which is usually machine id).
uname -i gives machine id and uname -a is more comprehensive way to look.
Thanks! (4 Replies)
hi,
I have a basic question,,
i am in a directory called
/intas/OCU_3.9.1/sbin
ocuut1@france>mv itsa_tcs itsa_tcs_old
mv: itsa_tcs_old: rename: Permission denied
i am logging as the owner of the file.
when i am doing this i am getting the above error of permission denied.
I know... (3 Replies)
sorry for being dumb here, but is there a way my for loop can take an entire line of a file into consideration instead of each word in a line... ill explain
if i have a file like this
# cat list
serial: 23124
hostname: server1
and a script that does this
# cat list.sh
#!/bin/sh
... (6 Replies)
greetings,
I am new to solaris, have a basic question.
I have to check for patch 137111-04 (as prerequisite) for installing Oracle.
# patchadd -p | grep 137111-04
# patchadd -p | grep 137111
Patch: 137137-09 Obsoletes: 120741-01 120986-12 120992-02 121008-02 121274-01 121414-01... (2 Replies)
Please have a look at below examples. Why do these 3 sed commands deliver the same result? Especially, why are there 4 "x" in the result instead of 3?
1.
echo "abc" | sed 's/d*/x/g'
xaxbxcx
2.
echo "abc" | sed 's/d*/&x/g'
xaxbxcx
3.
echo "abc" | sed 's/d*/x&/g'
xaxbxcx
Thanks for... (2 Replies)
Hi,
I have a months worth of data that I need to separate into weekly files. There is a date column with dates in the following format: YYYYMMDD.
I'm thinking I can create the weekly files by using a grep command combined with an IF command and specify each day of the specific week I'm... (1 Reply)
Discussion started by: cwl
1 Replies
LEARN ABOUT CENTOS
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS --help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN Debian Utilities CHECKBASHISMS(1)