Instead of setting the max_user_watches in a separate file in /etc/sysctl.d, as spideroak seems to be doing, you can define it in /etc/sysctl.conf.
If you define it this way, it won't cause any errors with procps and in addition it makes life easier if you have multiple realtime sync/backup applications running on your system (spideroak, Copy, dropbox, crashplan, whatever) $ sudo vi /etc/sysctl.conf # Increase max_user_watches, required for realtime backup/sync applications such as spideroak and crashplan fs.inotify.max_user_watches=1048576 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157643 Title: procps fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
