[22:01] <myndzi> i put a mistaken 'expect fork' in a script and now it just plain won't launch or anything even after i fixed it, used stop -n, ensured the process was killed, etc.
[22:01] <myndzi> ideas?
[22:04] <myndzi> well nm that, reboot took care of it... now how can i figure out why the process is ending when i can't seem to reproduce it from a shell?
[22:36] <ion> As for your first question, https://github.com/ion1/workaround-upstart-snafu
[22:37] <ion> As for the second one, “expect” has some very specific requirements for the forking behavior of the process. If it does not follow them, problems will ensue.
[23:07] <myndzi> first = thanks, second = got it working after a number of reboots
[23:07] <myndzi> but now i have a slightly different problem
[23:08] <myndzi> which is that it's not starting on startup
[23:09] <myndzi> i've also got this - init: /etc/init.conf: Unable to load configuration: No such file or directory
[23:09] <myndzi> uncertain if related?
[23:18] <myndzi> okay, i think i figured what's going on
[23:18] <myndzi> i wanted to run as another user, so i used 'su'
[23:19] <myndzi> it doesn't appear to like that, perhaps because the daemon is getting spawned many levels deep or something, dunno
[23:19] <myndzi> but it's some old version on centos 6.5 so i can't use setuser or whatever the commands are
[23:47] <myndzi> okay, i just made it not bother with daemonization
[23:47] <myndzi> or rather, it runs the app directly
[23:47] <myndzi> when i stop it it says stopped but the process is still running??
[23:57] <myndzi> daemonize answered my problems :P