- 2012-08-19: Working on the new Drupal 8 Entity system at Drupalcon Munich
- 2012-06-15: Working on the new Drupal 8 Entity system at DrupalDevDays Barcelona
- 2012-03-23: Working on the future Drupal Document Oriented Storage at DrupalCon Denver. D8 or later ? Bets are on.
- 2011-09-01: Building an Unfuddle to Drupal Casetracker import module using Migrate
- 2011-08-28: Back from DrupalCon London and its WSCCI code sprint. Wow.
- 2009-11-29: mongodb_watchdog module created by dereine, ported to D7 by me in about half an hour, and migrated in a larger MongoDB project by damz before the hour ended. Wow...
While browsing my servers Munin reports, I recently noticed how used disk space was constantly increasing on a filesystem which should not have been seeing such growth. After a bit of digging, it appeared the
/usr/local/var/varnish/(host) directory was filled with dozens of sparse files all named
varnish.??????. What could have been happening ?
Much like many Drupal devs, I happen to make fairly intensive use of Dropbox, and even use a "pro50" account to sync my always increasing set of "current" source folders, including checkouts of all major Drupal versions and lots of contrib.
Which means that, beyond the number of gigabytes of data Dropbox has to sync, the number of the files making up these gigabytes has also been increasing, currently to around 100k files. After I started playing with checkouts of the Drupy project in preparation for the Drupyx experiment, I noticed that, when I created some new files under the Drupy directories, their creations and subsequent changes would not be tracked by Dropbox, but they would correctly sync if I renamed the Drupy directory itself or a directory above it. Something like this:
|Action||Result on Dropbox.com|
|mv ~/Dropbox/src/drupy/src/foo.py ~/Dropbox/src/drupy/src/bar.py||Ignored|
|mv ~/Dropbox/src/drupy ~/Dropbox/src/drupa||Full sync below ~/Dropbox/src/drupa|
|mv ~/Dropbox/src/drupa ~/Dropbox/src/drupy||Full sync below ~/Dropbox/src/drupy, including "foo.py"|
And all this while operations on a PC running Windows tied to the same account did not experience any similar problem. What could be going wrong ?
I've been keeping track of various technical stats for OSInet's sites for as long as they've been existing (and that means well over 10 years, mind you !), and the June figures show a long expected landmark has been reached : for the first time since the creation of these sites, the operating systems declared as being Unix-ish by user agents (browsers) visiting our sites in June 2008 has broken the 10% barrier (10,08% to be accurate).