Need Help... I am getting a bad substitution error on my script on a Solaris Server. However the script has been proven to work on HPUX and Solaris servers...
#!/usr/bin/sh
#
# Set the location of the tzupdater.jar file
#
JAR=/tmp/tzupdater.jar # <<<<< UPDATE THIS LINE... (3 Replies)
I've created a series of arrays named as follows:
row1
row2
row3
.
.
.
row10
Each has 4 elements.
I'm trying to echo the array elements out in a for loop. Here's what I have:
for ((i=1;i<=10;i++))
do
for ((j=1;j<=4;j++))
do
eval out=${row`echo $i`}
echo -n $out (3 Replies)
hi,
i created a shell script having the following content:
#! /usr/bin/ksh
FROM="myemail@domain.com"
MAILTO="someemail@domain"
SUBJECT="TEST"
BODY="/export/home/adshocker/body.txt"
ATTACH="/export/home/adshocker/attach.prog"
echo $ATTACH
ATTACH_NAME="${ATTACH##*/}"
echo $ATTACH_NAME... (5 Replies)
Hello,
In bash I can use the following:
TMP=12345
MID=${TMP:1:1}
the expected result is: 2
but when using KSH I'm getting a ''bad substitution" error.
What is the correct syntaxin ksh?
Thanks (2 Replies)
#!/bin/bash
a1=( win 12,01,02,03,04 )
a2=( pre 04,05,06 )
a3=( msn 06,07,08,09 )
Given the above arrays, I want the script to return/echo the following in a loop;
win
12,01,02,03,04
pre
04,05,06,07
msn
06,07,08,09
But I can't get it to do as such.
I've tried; (2 Replies)
Hi All,
I'm building a new shell script but i'm facing a problem with one line which is giving "bad substitution" error. Please assist
script lines:
#!/bin/sh
printf "%s: " "Occurrence DATE (YYYYMMDD)"; read DATE
shortdate=${DATE#??}
o/p:
./test1: bad substitution
This command is... (2 Replies)
Hi,
I have a make file which I try to execute, but it failed when it arrived to the line:
for r in ${PIPESTATUS
}; do if (($r != 0)); then exit $r; fi;done;
With the Error:
""make:/bin/sh: Bad substitution""
Or the Error:
"make:${PIPESTATUS[...}: Bad substitution"
(Depend on the operating... (3 Replies)
Cant undestand :) why i have an error on line 2.it is working on my other boxes
#!/bin/bash
ret=$(echo Q | timeout 5 openssl s_client connect "${1`hostname`}:${2-443}" -ssl3 2> /dev/null)
if echo "${ret}" | grep -q 'Protocol.*SSLv3'; then
if echo "${ret}" | grep -q 'Cipher.*0000'; then
... (7 Replies)
i am trying to prepare a train and test dataset, for which i need to randomly split the data into corresponding folders (train,test)..
I began on a simple script, but seem to get som weird error messages, that i cannot make sense of?..
what am I doing wrong?
#!/bin/bash
RED='\033]
then... (13 Replies)
ShellCheck doesn't find any issues with this script.
#!/bin/bash
# color_meanings: explain meanings of colors used in bash ls
eval "$(echo "no:fi:di:ln:pi:so:do:bd:cd:or:mi:su:sg:tw:st:ex" | sed -e 's/:/=/g; s/\;/\n/g')"
{
IFS=:
for i in $LS_COLORS
do
... (18 Replies)
Discussion started by: Xubuntu56
18 Replies
LEARN ABOUT OSF1
badsect
badsect(8) System Manager's Manual badsect(8)NAME
badsect - Creates files to contain bad sectors
SYNOPSIS
/usr/sbin/badsect bbdir sector...
DESCRIPTION
The badsect command makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which
provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is preferable to use that
method to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1).
The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of
file systems or in swap areas.
On some disks, adding a sector that is suddenly bad to the bad sector table currently requires the running of the standard formatter.
Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be used to good
effect.
Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory. Make a direc-
tory BAD there. Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector numbers
must be relative to the beginning of the file system, as reported in console error messages.) Change back to the root directory, unmount
the file system, and run fsck(8) on the file system. The bad sectors should show up in two files or in the bad sector files and the free
list. Have fsck remove files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files. This operation will
leave the bad sectors in only the BAD files.
The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block
address is the block containing bad sector and whose name is the bad sector number. When fsck discovers the file, it will ask "HOLD BAD
BLOCK?" An affirmative response will cause fsck to convert the inode to a regular file containing the bad block.
RESTRICTIONS
If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks in the
bad sector files cover all the sectors in a file system fragment.
ERRORS
The badsect command refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued
if the block is already in use.
SEE ALSO
Commands: fsck(8)badsect(8)