From damianm at esi.com.au Fri Mar 4 17:12:35 2011 From: damianm at esi.com.au (Damian McGuckin) Date: Fri, 4 Mar 2011 17:12:35 +1100 (EST) Subject: [albatross-users] Installing Albatross In-Reply-To: <20110202014052.944B720588@longblack.object-craft.com.au> References: <20110202014052.944B720588@longblack.object-craft.com.au> Message-ID: Running python setup.py install Does not install the startup script as this is very much OS dependent. For 1.40, it it slightly more complicated as it demands that the user albatross exists. After adding a group albatross to /etc/group as group 199, I then did useradd -d /var/tmp -g albatross -c Albatross -u 199 albatross If anybody has a better idea, let me know. The use of 199 may clash. Pacific Engineering Systems International, 277-279 Broadway, Broadway NSW 2007 Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here ! Views and opinions here are mine and not those of any past or present employer From andrewm at object-craft.com.au Thu Mar 10 11:54:25 2011 From: andrewm at object-craft.com.au (Andrew McNamara) Date: Thu, 10 Mar 2011 11:54:25 +1100 Subject: [albatross-users] Installing Albatross In-Reply-To: References: <20110202014052.944B720588@longblack.object-craft.com.au> Message-ID: <20110310005425.6B4D322006@longblack.object-craft.com.au> >Running > > python setup.py install > >Does not install the startup script as this is very much OS dependent. Yep - and it even varies from distribution version to version - Ubuntu has moved to upstart, RedHat moved to upstart(?) and is now planning to move to systemd (FC16). I'm not sure where things stand with Debian - they were migrating to upstart, but it's taking a long time. OS X and Solaris have their own launch systems (example rules for which are included in the "mac" and "solaris" subdirectories). I thought I had included upstart rules in the distribution, but I can't find them now. >For 1.40, it it slightly more complicated as it demands that the user > > albatross > >exists. After adding a group > > albatross > >to /etc/group as group 199, I then did > > useradd -d /var/tmp -g albatross -c Albatross -u 199 albatross > >If anybody has a better idea, let me know. The use of 199 may clash. No, I think that's your best bet. The requirement for a user is specific to that init.d script - it probably should be documented in the script comments. Note that GNU useradd creates a group for the user if -g isn't specified and USERGROUPS_ENAB is set in /etc/login.defs (it's set in Ubuntu and RHEL), so it might be enough to just do: useradd -d /var/tmp -c Albatross albatross -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/