Finding non ascii characters in a text file

stackoverflow link
http://stackoverflow.com/questions/3001177/how-do-i-grep-for-all-non-ascii-characters-in-unix


My favorite out of this:
grep -P "[\x80-\xFF]" file.xml


This was really useful when compiling AWS Cloudformation templates since you can't have certain characters in the JSON.

Comments

Post a Comment

Popular posts from this blog

YAML Syntax Highlighting in gedit

Reference URLS: http://blog.dentcat.com/2009/09/highlighting-yaml-in-gedit_02.html http://codesauce.com/posts/gedit3-yaml-syntax-highlighting/ http://superuser.com/questions/353391/custom-gedit-syntax-highlighting-for-dummies sudo yum install subversion cd /tmp && svn checkout http://masood.googlecode.com/svn/trunk/yaml-language-spec/ cd yaml-language-spec/ sudo cp yaml.lang /usr/share/gtksourceview-3.0/language-specs/ sudo chmod 644 /usr/share/gtksourceview-3.0/language-specs/yaml.lang
Read more

Fedora - VNC through systemd/xinetd

Configuring Fedora 17 for Xvnc through systemd/xinetd I found a number of links around but nothing exactly covered my setup.  I wanted to be able to run an X11 session from home as securely and efficiently as possible.  After configuring my home server like this: sudo yum install xinetd tigervnc-server-minimal sudoedit /etc/gdm/custom.conf [security] RelaxPermissions=0 [xdmcp] Enable=1 HonorIndirect=1 [greeter] Quiver=1 sudo useradd -d /var/empty/vncuser -m -s /bin/false vncuser sudoedit /etc/services vnc-1280 5910/tcp # VNC Listener sudoedit /etc/xinetd.d/vnc # BEGIN service vnc-1280 { socket_type = stream protocol = tcp wait = no user = vncuser server = /usr/bin/Xvnc server_args = -inetd -query localhost -desktop 1024x768x24 -once -geometry 1024x768 -NeverShared securitytypes=none } # END sudo systemctl start xinetd.service And you will need to restart GDM.  I couldn't get the systemctl restart prefdm stuff quite right, so I reboote...
Read more

Sun Java memory fun with logstash

I am working on a distributed logstash deployment in AWS. I'm using the Elasticcache-Redis provided by AWS as the store between the syslog receiver and the elasticcache writer (aka the worker). I keep getting OOM errors on the worker like this {:timestamp=>"2013-10-22T08:18:58.592000+0000", :message=>"Failed to flush outgoing items", :outgoing_count=>34, :exception=>java.lang.OutOfMemoryError: Java heap space, :backtrace=>[], :level=>:warn} I was aware of the ability to change the heapsize allocated to the jvm, but wasn't sure how to find it.  Luckily google helped.  I took the command line I was using to run elasticsearch and compared how the 3 settings affected the defaults java -Xms512m -Xmx512m -Xss256k -XX:+PrintFlagsFinal -version > /tmp/1 java -XX:+PrintFlagsFinal -version > /tmp/2 diff /tmp/1 That helped me figure out which default settings were important. Now, I just have to figure out how to give logstash enough ...
Read more