[16:12] <gdoubleu> is there any documentation out there about how to run with additional upstart scripts in a directory outside of /etc/init?
[16:15] <gdoubleu> from the FAQ about symbolic links in /etc/init it seems that this is only possible with user jobs
[16:15] <gdoubleu> but I'm not seeing any docs about user jobs
[16:31] <marrusl> gdoubleu, take a look here:  http://upstart.ubuntu.com/cookbook/#running-upstart-as-a-non-privileged-user
[16:33] <marrusl> note: as mentioned there, it's designed for testing only.
[16:35] <gdoubleu> marrusl, and is running as a non-privileged user the only way running scripts from another directory is possible?
[16:35] <gdoubleu> I'm using RHEL6 here, where the upstart version is only 0.6.5
[16:35] <marrusl> gdoubleu, so it seems.
[16:36] <marrusl> gdoubleu, ah, so even that would not work.\
[16:37] <gdoubleu> marrusl, do you know if it's possible to put upstart conf files within a subdirectory under /etc/init, e.g. /etc/init/myproj/*.conf
[16:39] <marrusl> gdoubleu, I've never tried a subdirectory.  worth a shot.  
[16:39] <gdoubleu> nm, just tried it and I guess it is.  just have to specify the directory name in front of the service name
[16:39] <marrusl> the cookbook does say "all system job configuration files must live in or below /etc/init
[16:39] <marrusl> nice.
[16:39] <gdoubleu> just tried a "start myproj/nginx" with a conf file at /etc/init/myproj/nginx.conf and it worked
[16:40] <marrusl> gdoubleu, that's pretty neat actually.  thx for bringing it up.
[16:42] <gdoubleu> now, it would be really cool if you could do something like "start myproj/" and startup all jobs in that subdirectory
[16:44] <gdoubleu> marrusl, thanks for the info.  I guess I just have to roll with subdirectories for now
[16:46] <marrusl> gdoubleu, yep.  I guess making sure all jobs are available from early boot (hence forcing all jobs under the rootfs)is a design decision you're not going to get around.