07-02-2010
I think this is the fix
chomp($output);
Since $output was the last field in the record you split, the newline is probably still attached as part of the filename (yes, a newline can be part of a filename.) The actual file name you're interested does not contain the newline. "filename\n" is quite a bit different than "filename". This is 97% guaranteed to work.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Iam facing following error.please see the below script and error.Iam unable to attach error message to mail and its not sending mail also.
vi Expedites_test.ksh
"Expedites_test.ksh" 49 lines, 2276 characters
#!/bin/ksh... (4 Replies)
Discussion started by: venu_cisco
4 Replies
2. UNIX for Advanced & Expert Users
helo
I install my product for koren language
I m uisng RHEL -4 operating system
now problem is whenever I open any file
vi filename
I got following error on the screen
E557: Cannot open termcap file
'vt100' not known. Available builtin terminals are:
builtin_ansi
... (1 Reply)
Discussion started by: amitpansuria
1 Replies
3. Shell Programming and Scripting
Hi All,
I am new to shell scripting,Could any of you help me on this below :confused:
--------------------
I need to write a shell script where i have open an url and grep for a particular word in the url and want to display it in a flatfile.
Eg: Want to open yahoo.com and grep for yahoo... (1 Reply)
Discussion started by: sumithra
1 Replies
4. Shell Programming and Scripting
Hi All,
If I use the "/usr/dict/words" inside the shell script, It is showing the error as,
grep: can't open /usr/dict/words
How can we resolve it?
Thanks & Regards,
Raja (2 Replies)
Discussion started by: Rajakct84
2 Replies
5. Red Hat
Hi,
I get errors while running xclock from a non root user:
# xclock --- this works fine
# su - girish
$ DISPLAY=:0.0; export DISPLAY
$ xclock
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Error: Can't open display: :0.0
$
I basically want to... (4 Replies)
Discussion started by: girish1428
4 Replies
6. Linux
Hello,
I am facing a problem with ssmtp mailing agent.
I have installed and configured ssmtp in my RHEL5.3 system. I have written a shell script which sends mail to a couple of email id's. The script uses ssmtp to send mails. When I am running the scipt manually i.e. sh <script_name>.sh then... (3 Replies)
Discussion started by: senrooy
3 Replies
7. Shell Programming and Scripting
Hi,
I am using File::Find to go through a very large tree.
I am looking for all xml files and open only those that contain a tag <Updated>. I then want to capture the contents of two tags <Old> and <New>.
My problem is, after I open the file and do the first grep for <Updated> (which does... (3 Replies)
Discussion started by: OldGaf
3 Replies
8. Emergency UNIX and Linux Support
Hi all
I am receivng following error while running openoffice on linux system
Please suggest and linux comman which can remove this error:
(I) x.org loaded video driver of...
(II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
(==) Depth 24 pixmap format is 32 bpp
(III) ... (2 Replies)
Discussion started by: manigrover
2 Replies
9. Shell Programming and Scripting
Hi ,
In a directory i've the files in the following format
pay:year:mon:11789604
pay:year:mon:17675644
---
and i need to get 4th part of the above file name
so i used awk command in the below code
#!/bin/ksh
for test_data in pay*
do
txt_awk = awk -F':' '{print $4;}' $test_data
... (7 Replies)
Discussion started by: smile689
7 Replies
10. UNIX for Dummies Questions & Answers
Hi all, 1st post here. I'm on Solaris and currently, I get the following error if I try to use vim to edit anything:
Error detected while processing function <SNR>6_initialize:
line 2:
E697: Missing end of List ']':
E116: Invalid arguments for function <SNR>6_defineOption
line 3:
E10:... (6 Replies)
Discussion started by: fred2028
6 Replies
VIS(1) BSD General Commands Manual VIS(1)
NAME
vis -- display non-printable characters in a visual format
SYNOPSIS
vis [-cbflnostw] [-F foldwidth] [file ...]
DESCRIPTION
The vis utility is a filter for converting non-printable characters into a visual representation. It differs from 'cat -v' in that the form
is unique and invertible. By default, all non-graphic characters except space, tab, and newline are encoded. A detailed description of the
various visual formats is given in vis(3).
The options are as follows:
-b Turns off prepending of backslash before up-arrow control sequences and meta characters, and disables the doubling of backslashes.
This produces output which is neither invertible or precise, but does represent a minimum of change to the input. It is similar to
``cat -v''.
-c Request a format which displays a small subset of the non-printable characters using C-style backslash sequences.
-F Causes vis to fold output lines to foldwidth columns (default 80), like fold(1), except that a hidden newline sequence is used,
(which is removed when inverting the file back to its original form with unvis(1)). If the last character in the encoded file does
not end in a newline, a hidden newline sequence is appended to the output. This makes the output usable with various editors and
other utilities which typically do not work with partial lines.
-f Same as -F.
-l Mark newlines with the visible sequence '$', followed by the newline.
-n Turns off any encoding, except for the fact that backslashes are still doubled and hidden newline sequences inserted if -f or -F is
selected. When combined with the -f flag, vis becomes like an invertible version of the fold(1) utility. That is, the output can be
unfolded by running the output through unvis(1).
-o Request a format which displays non-printable characters as an octal number, ddd.
-s Only characters considered unsafe to send to a terminal are encoded. This flag allows backspace, bell, and carriage return in addi-
tion to the default space, tab and newline.
-t Tabs are also encoded.
-w White space (space-tab-newline) is also encoded.
SEE ALSO
unvis(1), vis(3)
HISTORY
The vis command appeared in 4.4BSD.
BUGS
Due to limitations in the underlying vis(3) function, the vis utility does not recognize multibyte characters, and thus may consider them to
be non-printable when they are in fact printable (and vice versa).
BSD
June 25, 2004 BSD