Strange sed behaviour Post: 302165553

9 More Discussions You Might Find Interesting

1. Linux

/etc/passwd strange behaviour!

Hi there, first of all, here is my conf of a uname -a Linux SAMBA 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown on a fedora machine. Here is my problem: every once in a while, the line containing root disappears in the /etc/passwd, disabling all logging on my server. Any one have...

2. Shell Programming and Scripting

A Strange Behaviour!!!

Can some-one give me a view to this : I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory. Now there is another directory basically the destination directory which has all the permissions. Note:I log in as not the owner,but user...

3. UNIX for Advanced & Expert Users

Strange KSH behaviour - any comments?

As you are probably aware, $# indicates the number of parameters passed into a korn shell script. But this appears to hang around for sunsequent runs...???? A simple script:- #!/usr/bin/ksh echo "#parameters $#" echo "\$1 $1" echo "\$2 $2" I run the script with 0 parameters (all fine) #...

4. UNIX for Dummies Questions & Answers

Strange Program behaviour

Had a strange thing going on with my code. It's ok I figured it out for myself....

5. Shell Programming and Scripting

strange behaviour from sed???

Hi all, I want to do a very simple thing with sed. I want to print out the line number of a disk I have defined in /etc/exports, so I do: It's all good, but here's the problem. When I define md0 in a variable, I get nothing from sed: Why is that? can anybody please help? Thanks

6. Shell Programming and Scripting

Strange behaviour with perl i/o?

Hi All, I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data. If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But...

7. HP-UX

Strange login behaviour

Hi all, I am using HP-UX and I have just noticed that when I log into the network it seems to save the previous windows that were subsequently closed on previous occasions. Does anyone know when I log in, it seems to display these previous windows, e.g. nedit windows open again? Does...

8. Shell Programming and Scripting

Strange RegExp Behaviour

Hello, I was trying to identify lines who has a word of the following pattern "xyyx" (where x, and ys are different characters). I was trying the following grep - egrep '(\S)()\2\1' This pattern do catches the wanted pattern, but it also catches "GGGG" or "CCCC" patterns. I was trying to...

9. Red Hat

Crontab strange behaviour

Hi all, I'm having this scenario which for the moment I cannot resolve. :( I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example. The script is like below: cat /home/oracle/scripts/db_backup.sh #!/bin/ksh ...

LEARN ABOUT DEBIAN

fixnt

fixnt(1)							      Debian								  fixnt(1)

NAME

       fixnt - Filter for the Windows NT postscript printer driver.

SYNOPSIS

       fixnt < BADFILE.ps > GOODFILE.ps

DESCRIPTION

       The  Windows  NT  postscript  driver has a tendency to make broken postscript files, that are incompatible with psutils.  fixnt is a filter
       that fixes these problems, allowing the use of psnup(1).

       The filter takes the broken postscript file on stdin, and outputs a fixed postscript file on stdout.  It has no other form  for	invocation
       and takes no options on the command-line.

OPTIONS

       fixnt  takes no options.

BUGS

       fixnt does not check for NTPSOct94.  For a workaround, use a sed(1) command to replace 'NTPSOct94' with 'NTPSOct95', like so:
	      sed 's/NTPSOct94/NTPSOct95/g'
       This is particularly important for Windows NT 3.5 users.

AUTHOR

       fixnt   was   written   by   Holger   Bauer   <Holger.Bauer@topmail.de>,  Michael  Rath	<rath@itsm.uni-stuttgart.de>,  and  Akim  Demaille
       <demaille@inf.enst.fr>.

REPORTING BUGS

       Report bugs to the Authors, but avoid sending large postscript files.

       Patches are always welcome; send to <bauer@itsm.uni-stuttgart.de>.

SEE ALSO

       psnup(1), sed(1)

a2ps								   February 2003							  fixnt(1)