After carefully looking around (A LOT) I found a code change in 2011 about making notify-osd not output by default to the log file because this was used for debugging purposes and wrote to the HDD every time it did. To activate this feature you can do it 2 ways, a temporary method and a more permanent one.
Temporary Method
Open the terminal I type the following:
For 64 Bit Systems:
sudo killall notify-osd
LOG=1 /usr/lib/x86_64-linux-gnu/notify-osd &
For 32 Bit Systems:
sudo killall notify-osd
LOG=1 /usr/lib/notify-osd/notify-osd &
Now you will see the .cache/notify-osd.log file and the debug information in it.
Permanent Method (WARNING: Global Change)
For a more permanent solution do the following (Global Change. Read the Warning mentioned by Rinzwind below. This will affect everyone and kill the cat!):
sudo nano /etc/environment
Add the following line at the end and save:
LOG=1
Reboot the computer to test.
Permanent Method (User Specific Change)
For a more permanent solution do the following (User specific Change. This will only affect you and the dog. The cat will still survive.):
sudo nano ~/.bashrc
Add the following line at the end and save:
LOG=1
Reboot the computer to test.
You should see the information start to appear in the .cache/notify-osd.log file. For example, this me after disconnecting 2 times my wired connection:
GNU nano 2.2.6 File: .cache/notify-osd.log
[2013-05-04T18:49:55-00:00, NetworkManager ] Connected
Intel
[2013-05-04T18:50:26-00:00, NetworkManager ] Disconnected - you are now offline
Ethernet network
[2013-05-04T18:50:29-00:00, NetworkManager replaced] Connected
Intel
Best Answer
Unless a command has output or logging already configured,
rc.localcommands will not log anywhere.If you want to see logs for specific commands, try redirecting the stdout and stderr for
rc.localto somewhere you can check. Try adding this to the top of your/etc/rc.localfile:Though this will require to rerun the
rc.localfile.