So...

I haven't posted anything, in a minute. Lol.

~W

OSX - Disabling Spindump and VM Compressor 

In case you need to do so. 

If you do, you'll know why. I'm not spending a lot of time getting into the why's and why-not's.  

Just putting this note here, for reference: 

VM Compressor: 
# nvram boot-args="vm_compressor=1" 
--reboot-- 

Check mode: 
# sysctl -a vm.compressor_mode vm.compressor_mode: 1 

------------------------ 

Spindump: 
# cd /usr/sbin/ 
# mv spindump spindump.bak 
# ln -s /usr/bin/true /usr/sbin/spindump 
# launchctl unload -w /System/Library/LaunchDaemons/com.apple.spindump.plist

Happy New Year....and stuff

Figured since I haven't given any love to my Blog in over a year, I'd stop by and tap it on the ass.

Mac OS X Mavericks and Yosemite running out of memory "fix"

Silly Mac OSX.

Clean up memory cache easily this way:

Add the following entry in your root's crontab:
# Clean up memory
30 * * * * /usr/sbin/purge &

Use at your own risk, but I have not had issues with it.

If you don't know how to update your root crontab, well, then you have no business running this. Use some 3rd party graphical app or something to clean up.

FYI: Some people are having issue with Chrome and Flash and other programs not "letting go" of reserved memory, after use. This will help alleviate the issue. Developers are arguing over it's use, claiming memory management is just fine in OS X 10 Mavericks and later. I beg to differ as I have seen memory run out several times myself with using Chrome web browser and it not letting resources go.

You can read more about it, here:
http://osxdaily.com/2013/11/14/use-purge-command-os-x-mavericks/

Flush your bash command history

Lose your terminal session? Did your VPN drop? Did you have a bunch of work you were doing in your bash session and because you lost connection, your session closed uncleanly and you wanted to retrieve your command history?

Yeah. Sucks, huh?

Here's a simple fix:

insert the following in your ~/.bashrc :

# vi ~/.bashrc

export PROMPT_COMMAND='history -a'

and resource:

# .~/.bashrc

There.

Now your commands will "flush" to the history file immediately.



You're welcome.

-Wrex

OSX Mavericks client AD Binding. Little "gotcha's" to look out for.

Make sure your OSX client is using the same time server (NTP) as the AD server(s) else you will get an error, such as:

"Unable to add server

Node name wasn't found

(2000)"

Also helpful is having the OSX client machine already in the DNS that the AD uses (Forward and reverse).

You're welcome. 

RDP in Ubuntu 13.04/13.10 (How to install xrdp and connect from Windows/OSX)

On the Ubuntu machine, install xrdp (via a terminal):

• sudo apt-get install xrdp

Install XFCE:

• sudo add-apt-repository ppa:xubuntu-dev/xfce-4.10
• sudo apt-get update
• sudo apt-get install xfce4

Configure your session to use XFCE:

• echo xfce4-session >~/.xsession  

Restart xrdp:

• sudo service xrdp restart

There. Quick and relatively easy fix.