[02:55] <dAndy> is there a way to make up start drop privileges to a non-root user before starting the process?
[03:18] <Amaranth> dAndy: that should be up to the process
[03:19] <Amaranth> doesn't start-stop-daemon do that for you, btw?
[03:23] <dAndy> i was under the impression that upstart made it so you dont need to use start-stop-daemon
[03:24] <dAndy> but that answers my question
[11:12] <ion_> This is a Unix system. I know this.
[11:13] <Keybuk> :)
[03:36] <Keybuk> damn, there's no event when a user is added to the system <g>
[06:49] <ion_> keybuk: echo '/sbin/initctl emit user-added "$1" -eUSERNAME="$1" -eUID="$2" -eGID="$3" -eHOMEDIR="$4"' >>/usr/local/sbin/adduser.local
[07:03] <Keybuk> lol
[07:03] <Keybuk> I was thinking from the point of view of detecting new users and watching their ~/.? directory
[07:03] <Keybuk> though I'm starting to think the /var/spool/? method might be needed
[07:05] <ion_> So the users would edit their personal upstart stuff via something like crontab(1) and access control would be implemented via something like /etc/cron.{allow,deny}?
[07:06] <Keybuk> dunno
[09:09] <Keybuk> AlexExtreme: after complex-event-config
[09:09] <Keybuk> which has a timeline of despair
[09:10] <AlexExtreme> hmm ok
[09:10] <Keybuk> since I want to get that out of the way, as it's the most important piece of the missing puzzle
[09:11] <AlexExtreme> sure
[09:11] <Keybuk> and still haven't reached a happy idea with that yet
[09:14] <ion_> We must add some Enterprise and XML.
[09:14] <ion_> And regular expressions, those will fix everything.
[09:17] <Keybuk> Write it in mono!
[09:20] <Keybuk> we could use RSS to define states