[02:14] hi. how can i get upstart to see my conf file? i created /etc/init/myserver.conf [02:14] but when i initctl list | grep myserver [02:14] i dont see it [02:18] Look at the error message in syslog. [14:50] hi all, my devs want to use perlbrew for running perl daemons out of - which need to run under the user nobody who has no shell. perlbrew uses a bashrc style file to setup its environment - is there a way to source the environment but not give the user a shell and still run under perlbrew whilst the process has been launched by nobody? [15:05] pixie79: yes [15:05] pixie79: you can setup the environment before you switch users very easily [15:06] ok that would be good, and keep the running user as a non login user for security? [15:06] pixie79: is there any reason you can't put the environment variables in the upstart job as env statements? [15:07] SpamapS: that is what i said but they seemed to think they would not be populated down to forked scripts which the dameon starts [15:08] of course it will [15:08] unless those daemons explicitly set an environment different than their own [15:14] thanks - i will take it back to them [15:22] does this make sense' start on started tty /dev/tty ' [15:22] or /dev/tty1 even [15:23] i seem to be in a mix where we have things on initctl but being started by init.d [15:29] hm [15:30] pixie79: why are you starting after tty? [15:30] pixie79: 99.9% of things should be 'start on runlevel [2345]' [15:30] yep i realised that after - although some things seem to start sometimes and not others [15:31] pixie79: if there are errors in any of the tracked processes, you'll see that in /var/log/syslog [15:32] SpamapS: what is the best way to tell init to wait for a user to exist before starting a process - i am thinking zabbix here - the user exists in ldap via sssd which seems to sometimes start later and then takes a few seconds to cache [15:33] wait for a user to exist? [15:33] pixie79: sssd is local? [15:34] sssd is a local daemon that caches ldap [15:34] which is remote [15:34] pixie79: sounds like the job should be retrying if it is meant to depend on a network service. [15:34] SpamapS: it is set to but seems to get stuck start/running - but is not running [15:34] pixie79: another option is to have sssd emit an event when it is ready to serve requests (if it is already an upstart job, 'started sssd') and start on that... but IMO, that becomes complicated. [15:35] ok - i might add a pre to do a getent passwd zabbix| grep zabbix and match if that is true [15:36] pixie79: best option might be to start sssd from a separate task that does 'start on starting rc-sysinit' .. that will make sure sssd is started before runlevel 2 [15:36] ok [15:37] pixie79: which it should be doing, because really if it provides user services, it should be started and operational before "multi user mode" [15:37] pixie79: where is sssd coming from, btw? a package or somewhere else? [15:37] yep - no i think redhat have just added it to init.d [15:37] but it would seem init kicks in before or at the same time [15:45] pixie79: what OS is this? [15:46] rhel 6.3 but under openvz [15:49] pixie79: yeah, so I'm not sure if rhel6.3 has 'rc-sysinit'.. [15:57] this seems to do the tick, after start on started sssd; in the zabbix script pre-start with if ! [ `/bin/sh -c '/bin/chmod 1777 /dev/shm'; sleep 10; getent passwd zabbix | cut -f 1 -d :` == "zabbix" ]; then echo "Zabbix User does not Exist yet" | logger -t ZABBIX -p daemon.info; stop; exit 0; fi [20:37] This is a horrible script ^