Sponsored Content
Full Discussion: sed is dead
Top Forums Shell Programming and Scripting sed is dead Post 302525212 by zaxxon on Thursday 26th of May 2011 04:58:48 AM
Old 05-26-2011
Nietzsche said that about god, not sed! Smilie

The variable is enclose by singe quotes so it will never be evaluated by the shell and sowith sed will never find a match - so no change to the file:
Code:
for k in ${MOLARRAY[@]}
do
    sed -i -e '/'${k}'/d' test2
done

This User Gave Thanks to zaxxon For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

Dead SUN

My SUN V210 refuses to fully boot up. We had a power outage (ie. someone tripped the cord) and thereafter the Sun will not come up, and the OS is not starting. The LED on the front is not lit. Monitor gets no feed, so I plugged in via the management port. The system comes up to: Trap 3e. and... (7 Replies)
Discussion started by: ireeneek
7 Replies

2. UNIX for Dummies Questions & Answers

dead.letter

HI, I am pretty new to Unix...but here is 1 serious problem...atleast for me..:-) now..the dead.letter file in /var/tmp has been growin continuously..n i dont know why..I ve even killed the sendmail process..but the dead.letter file keeps on increasin..Can anyone tell me where do I start... (6 Replies)
Discussion started by: unisam
6 Replies

3. UNIX for Dummies Questions & Answers

Jack Kilby dead at 81

If Edison and Ford were the the greatest inventors and influencers of the turn of the 20th century... then surely Jack Kilby was probably the most influential person of the late 21st century and for time immemorial...on our way of life. A legend dies (7 Replies)
Discussion started by: Kelam_Magnus
7 Replies

4. Filesystems, Disks and Memory

Dead partition on drive

We are still using solaris 1 with sunos 4.1.4 because nobody here knows Unix. My colleague did a backup (dump) to the wrong place (/dev/sd0h) and we lost this part of the drive. The information is still on tape but we cannot repartition the /dev/sd0h. fsck keeps on about the "wrong SUPER BLOCK"... (2 Replies)
Discussion started by: Tom Bekaert
2 Replies

5. Shell Programming and Scripting

what is dead.letter ??

Hi all can you please help me what is dead.letter file ? when it is created ? for the first time i have seen this file getting created in my current directory? I am using SunOs. Any IDEA ?? (2 Replies)
Discussion started by: jambesh
2 Replies

6. Filesystems, Disks and Memory

Dead SCSI drive

I have 2 dead SCSI drives. Can anyone tell me a good way to repair the disks??? Please! (1 Reply)
Discussion started by: disturbe_d
1 Replies

7. What is on Your Mind?

Usenet is dead

On servers i check there seems to be no news at all. (3 Replies)
Discussion started by: Action
3 Replies

8. Post Here to Contact Site Administrators and Moderators

Dead link in FAQ

Dead link from FAQ, then Technical FAQ: Senior Advisor - https://www.unix.com (Was about to suggest that a O/P read this FAQ). (9 Replies)
Discussion started by: methyl
9 Replies

9. Shell Programming and Scripting

showing dead accounts?

Got a quick question. How do you shows dead accounts (false shells) and how do you include a count at the end? (1 Reply)
Discussion started by: JA50
1 Replies
BASHBUG(1)						      General Commands Manual							BASHBUG(1)

NAME
bashbug - report a bug in bash SYNOPSIS
bashbug [--version] [--help] [email-address] DESCRIPTION
bashbug is a shell script to help the user compose and mail bug reports concerning bash in a standard format. bashbug invokes the editor specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill in the appropriate fields and exit the editor. bashbug then mails the completed report to bug-bash@gnu.org, or email-address. If the report cannot be mailed, it is saved in the file dead.bashbug in the invoking user's home directory. The bug report format outline consists of several sections. The first section provides information about the machine, operating system, the bash version, and the compilation environment. The second section should be filled in with a description of the bug. The third sec- tion should be a description of how to reproduce the bug. The optional fourth section is for a proposed fix. Fixes are encouraged. ENVIRONMENT
bashbug will utilize the following environment variables if they exist: EDITOR Specifies the preferred editor. If EDITOR is not set, bashbug defaults to emacs. HOME Directory in which the failed bug report is saved if the mail fails. TMPDIR Directory in which to create temporary files and directories. SEE ALSO
bash(1) AUTHORS
Brian Fox, Free Software Foundation bfox@gnu.org Chet Ramey, Case Western Reserve University chet@po.cwru.edu GNU Bash-4.0 1998 July 30 BASHBUG(1)
All times are GMT -4. The time now is 03:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy