Random technical rants, comments, and logs. If these only serve as a reference for me later, I still call that a win. Hopefully, others will occasionally find the posts useful.
I have a Netgear WNDAP360 ap which is pretty hard core for home use. It was an upgrade from a previous netgear prosafe ap that just 802.11b/g. The WNDAP360 is 802.11a/b/g/n and supports dual radio data pathing for much faster throughput. When I had just the single radio AP I used 2 different SSIDs, one for the trusted wireless network at home and one for the untrusted. Why 2 for home? Well, when family members visit with Microsoft boxes they clearly get put on untrusted, while Linux and Apple generally go on the trusted side. So when I implemented the dual radio AP, I initially created SSIDs with the same name on each of the different radios. So for the A radio, I used untrusted and trusted SSIDs. Then on the B radio, I used untrusted and trusted. I figured that devices would happily discover both untrusted and both trusted and pick the radio that was the fastest. In practice however, that was not the case. Devices seemed to lock...
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...
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 ...
Comments
Post a Comment