Recently, I had a chance to be in a room with a bunch of Ph.D. students and faculty members from the mechanical engineering department. Faculty members were presenting their research to other faculty members and Ph.D. students.

Updates

Updates

Due to the growing aging population, non-pharmacological interventions to prevent diabetes-related disability are critical if we want to reduce costly healthcare use and excess mortality. When reviewing existing preventive interventions, there are two things that need to be kept in mind.

Modernism and Postmodernism, which began in the late 1950s and the mid-1970s, have influenced the development of disability models. In this post, I introduce the similarities and differences between disability models in the late 20th century and explain how rehabilitation sciences mirror Modernism and Postmodernism.

If you own an SSH server and that machine is behind a VPN, then without any special setup you are not able to SSH to it with its original public IP from a client outside the VPN. An easy solution is to disconnect the machine from the VPN so clients outside the VPN can access it. But what if you really want to keep using the VPN on that machine?

Recently, PulseAudio often refused to start because the system ran out of inotify watches. I tried to Google this issue and found that most posts simply told me to increase the allowance of inotify watches. I was not satisfied with this. I wanted to know the underlying cause of this issue. That is, why the default allowance (which is 8192) was not enough and, also, what program was responsible for running out of inotify watches. Knowing this information, I may be able to find a better solution, instead of blindly increasing the allowance without knowing who is using it. After googling, I found some posts talking about how to know what processes/programs are using inotify. But I could hardly find posts about how to know HOW MANY INOTIFY WATCHES ARE USED BY EACH OF THOSE PROCESSES/PROGRAMS. I finally found one in a reply in this thread. The author of that reply spent a lot of words explaining the idea behind his/her solution. I re-organized the information, eliminated those explanations, and kept only the method. By this method, I finally found out who is responsible for running out of inotify watches: Insync. I got over 50K files in the sync folder of Insync, and so Insync used over 12.5K watches, which exceeds the default allowance, 8192.

Updates