02-13-2019
Hi Alex,
Welcome to the UNIX.com forum.
When starting a new thread here, please always tell us what operating system you're using and what shell you're using. Various common utilities behave differently on various operating systems and when run by various shells. Many utilities have options that are available on some operating systems but not on others. If we don't know what environment you're using, we have to guess at what might be happening to you.
You say that you have been running runvdr for years. What has changed since the last time you ran it successfully? Did you install any new software packages, system or application updates, start using a different shell?
What exact command did you use to invoke runvdr?
Exactly what diagnostic messages did it produce when you invoked it?
When the shell tells you it was expecting a }, it usually means that sometime before it issued that complaint it had found a { and it hasn't found a match for it yet to finish what it had been told to do. With the complete diagnostic message and the contents of the script you're running, we might have a much better chance of helping you figure out what happened.
Last edited by Don Cragun; 02-13-2019 at 03:49 PM..
This User Gave Thanks to Don Cragun For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
Discussion started by: Lokesha
4 Replies
2. Shell Programming and Scripting
I have a very simple script that reads in the contents of a file (_open.txt) into an array "lyrics":
#!/bin/sh
# read in the text
lyrics=( `cat _open.txt` | tr '\n' ' ')
exit 0
It gives the following error message:
./lyrics.sh: 1: Syntax error: word unexpected (expecting ")")
I have... (9 Replies)
Discussion started by: figaro
9 Replies
3. Shell Programming and Scripting
hi All,
cat file_name | awk /^~/'{print $1","$2","$3","$4}' | sed -e 's/~//g'
Can this be done by using sed or awk alone (4 Replies)
Discussion started by: harshakusam
4 Replies
4. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
5. Shell Programming and Scripting
logs:
"/home/abc/public_html/index.php"
"/home/abc/public_html/index.php"
"/home/xyz/public_html/index.php"
"/home/xyz/public_html/index.php"
"/home/xyz/public_html/index.php"
how to use "cut" or "awk" or "sed" to get the following result:
abc
abc
xyz
xyz
xyz (8 Replies)
Discussion started by: timmywong
8 Replies
6. Solaris
The system don't boot.
on the screen appears following:
press enter to maintenance (or type CTRL-D to continue)...I checked with format command.
... the slices "0-root","1-swap","2-backup" exist.
...the slises "3-var","6-usr" -unassigned. :( (16 Replies)
Discussion started by: wolfgang
16 Replies
7. UNIX for Dummies Questions & Answers
How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address
and column 3 contains “cc” e-mail address to include with same email.
Sample input file, email.txt
Below is an sample code where... (2 Replies)
Discussion started by: asjaiswal
2 Replies
8. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
9. AIX
Hi 2 all,
i have had AIX 7.2
:/# /usr/IBMAHS/bin/apachectl -v
Server version: Apache/2.4.12 (Unix)
Server built: May 25 2015 04:58:27
:/#:/# /usr/IBMAHS/bin/apachectl -M
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
mpm_worker_module (static)
... (3 Replies)
Discussion started by: penchev
3 Replies
dosif(4) Kernel Interfaces Manual dosif(4)
NAME
DOSIF - DOS interchange format
DESCRIPTION
The DOS Interchange Format (DOSIF) is the name given to the media format used by the DOS operating system. This format is based upon that
used in IBM PC and PC AT and HP Vectra systems.
Use the and commands to convert files between HP-UX and DOS file formats; see dos2ux(1). Use these utilities to retrieve information from
a DOSIF volume.
The dos*(1) utilities are the only HP-UX commands that can interact directly with the contents of a DOSIF volume. The only other way to
interact with the contents of a DOSIF volume is to use an HP-UX DOS emulation or coprocessor facility such as SoftPC or the DOS Coproces-
sor. The command cannot be used on a DOSIF volume because the operating system does not recognize it (see mount(1M)).
When constructing file names for the dos*(1) commands, start with the HP-UX path name of the DOSIF volume, then add a colon followed by the
file name:
or
This file naming convention is suitable for use only in arguments of the dos*(1) utilities. It does not constitute a legal path name for
any other use in HP-UX applications.
Metacharacters and can be used when specifying both HP-UX and DOS file names. These must be quoted when specifying a DOS file name,
because file name expansion is performed by the DOS utilities, not by the shell. The dos*(1) utilities expand file names as described in
regexp(5) in the section.
By convention, if the HP-UX device name and a trailing colon are specified, but no file or directory name is provided (for example, the
root of the DOS file system is assumed.
EXAMPLES
Example 1
Specify DOSIF file accessed through HP-UX special file
Example 2
Specify DOSIF file accessed through the DOS volume stored as HP-UX file
SEE ALSO
dos2ux(1).
dosif(4)