I didn’t knew it existed until recently, that I saw all my memory was eaten up and suddenly I was using my SWAP instead of my memory, and it was fully loaded.

What’s my surprise? I have 2G in memory and 1113M of it was cache, and 1G of swap full as well. The worst thing is that I reboot my machine and without starting anything I get 903M of cache full, out of nowhere!

I start to track what’s the issue, where’s the leak, and found that if I killed tracker-store early then my memory stopped being loaded of cache.

There’s a bug, already reported, it’s #612242 and the workaround given is to nuke the database with tracker-control -r.

It worked. Now my cache is not full, but since I just did it I don’t know if in some days my tracker-cache will be full again and eating all my memory.

Just wanted people know there was a work-around at least and you could use your computer again.

The reason was the trailing slash in proxy_pass variable. So, instead of

proxy_pass http://127.0.0.1:88334/;

You should use

proxy_pass http://127.0.0.1:88334;

That fixed my issue, didn’t had time to do further investigation, but that’s a workaround for that issue.

Since in my applications I serve cookies already where I save session info and this is already stored in Redis with help of the module connect-redis then I should be able to get this info onto Socket.IO authorization method and with this allow only to authorized users to get info from my websockets.

I found how to do it with the default session-store in-memory from Express, and adapted that so it could work with Redis.

Here’s the snippet:

Hope anyone can found it useful!

I was searching through the internet what was I doing wrong, I wrote to the polipo-user list but my email got stuck on moderation, and my connection is really shitty (that’s why I’m using polipo the way I’m using it). I have relaxTransparency and mindlesslyCacheVary set to true, but I don’t need so aggresive caching in my development stages that are located under *.local and another development subdomain on the net.

Already tried setting uncachableFile to /etc/polipo/uncachable and to ~/.polipo-uncachable, according to the web-config thing is properly setted up, but can’t get it to recognize it’s content. I first thought it was I was writing bad the regex, .*\.local but it does work in the /etc/polipo/forbidden file. Besides, adding complete domains to the uncachable file doesn’t works neither. Could someone confirm this or throw me a hand on this? I’m using 1.0.4.1-1.1 version which is the last one on unstable repos.

I must admit I was happy, I really was. I was used to my workflow with 4 terminals 8×25 and a bunch of screens, with several nested-screens. I used awesome-wm before, so definitely I felt I wasn’t using all the space in my laptop screen (my laptop is a ThinkPad X61, so 1024×768 in a 12 inches-screen) but that was OK, after all my workflow was, well, good.

Until 2 days ago, I was told to try tmux, in fact, I was told «and why are you using screen? use tmux». As a daily-user of Screen my first reaction was «I’m used to», «I can use it as I want», and a lot of excuses for just not trying something new. But then I made a little research (on Google, of course). In about 30 minutes I ended up with a multiplexer working as I wanted and as I never got Screen to work. Finally I was using just a terminal and using all the space available in my tiny-laptop-screen and plus: saving a lot of bandwidth with my permanent SSH connection (a really big plus now that I’m living with a capped link to the net with a GSM-modem).

I changed the Ctrl-b shortcut to Ctrl-a (b is too far for using it with only one hand), configured so I could use nested tmux’es like screen when I push Ctrl-a a, activated visual monitoring and even got to use the tmux’s buffer along with my X11 buffer when I press Ctrl-a >!!

It’s all in my ~/.tmux.conf, use it at will. Later I will make a screencast about using tmux, so more people can get a working tmux easily.

ATM, I’m even more happy than I was with GNU Screen, so, any other recommendation, people?

});

What it does the script?

Finds the active-tab identified with the .ui-state-active class and then changes the img tab src attribute according to the href attribute of the active-tab.

Content


img#bg {
min-width: 100%;
min-height: 100%;

z-index: -1;
}


What does it does?

It takes an inline image and uses it as if were a background-image thanks to the z-index: -1 CSS-rule.

There are lots of other techniques at CSS-Tricks but none works in every browser as this one in particular.

Enjoy.

But that was when I got a stable connection at >100KiB/s in a daily-basis. Now I’m with a mobile connection at <30KiB/s and sometimes is intermittent, so approx started giving me a lot of headaches.

When approx tries to connect a host that can't be resolved its domain name, then gets 404. How does that reflects in the /pool? Well, you get a file touch'd and 0 bytes size. When you try again, approx will find the same file with 0 bytes size and will gives you again a 404, even if you can now resolve the name address of that domain. And as I like to use what I know, then I made a workaround: Each time this happened I ran:

# find /var/cache/approx -size 0 | xargs rm

So next time I requested a file to approx it tried to connect to the host. But I got tired.

I installed apt-cacher-ng, tweaked a bit /etc/apt-cacher-ng/acng.conf so it uses port 9999 and the cache dir redirects to the same cache than approx and done. apt-cacher-ng returns 503 when it can't connect to the peer, even tries to several repositories with only a line in /etc/apt/sources.list in my clients. It makes me happy and keeps saving me a lot more of bandwidth than approx.

La librería en cuestión se llama Deck.js y pueden ver una demostración de sus resultados, incluye más temas y documentación para que tú mismo crees tus temas si manejas CSS+JS.

Pueden hacer un fork del código de Deck.js desde GitHub.