[09:41] <afournier> hi
[09:42] <afournier> i think i have a leak in upstart, an old version of it 1.6.1 on i686, any known bug about that ?
[09:42] <afournier> root         1  0.0 20.2 684228 682496 ?       Ss   Feb25   2:34 /sbin/init
[09:43] <afournier> pmap => 80c70000  680804       -       -       - rw---    [ anon ]
[16:08] <macdabby_> im having an issue with mongo that seems to be related to upstart ... "mongod --config /etc/mongod.conf" works but "service mongod start" fails because it's not loading the config file.
[16:08] <macdabby_> i added an echo to the upstart file and this seems to be what it's executing: mongodstart-stop-daemon --background --start --quiet --pidfile /var/run/mongod.pid --make-pidfile --chuid mongodb --exec  /usr/bin/mongod  -- --config /etc/mongod.conf
[19:10] <cetex> hm.. any ideas how i should setup an upstart job that can be started without any instance variables set, and which can handle multiple instances as well?
[19:11] <cetex> I need something where an upstart job can be started without setting any extra parameters, and i need to identify this, i then need to be able to create instances of the same job that behaves differently.
[19:28] <cetex> ah.. set an environment variable to something defaultish, use that as instance, then set it to other variables when triggering new events.