mythbuntu-bugs team mailing list archive
-
mythbuntu-bugs team
-
Mailing list archive
-
Message #03611
Re: [Bug 668810] Re: can't set environment variables in startup
On Wed, Nov 17, 2010 at 06:32, Brian J. Murrell
<brian@xxxxxxxxxxxxxxx>wrote:
> On Wed, 2010-11-17 at 04:44 +0000, Mario Limonciello wrote:
> > A lot of the philosophy behind upstart is that the jobs are simple
> > enough that local admins can make changes and easily be able to merge
> > them if they update versions.
>
> Yeah. The need to merge on every single update. That's a PITA that
> does not exist when these changes are sourced from a non-update (and
> therefor non-conflict) location.
>
> > This doesn't sound like much of a regression across the old init.d
> > script based on the above.
>
> It is when you account for the need to merge on every update vs. having
> updates installed completely hands-off.
>
> Fortunately the scripts don't change very often. You should only have to
merge updates when they do. Eg if you have auto-builds enabled, you
shouldn't be having to change it daily.
> > You still had to modify the init.d script to
> > declare any proxy variables etc.
>
> No I didn't. The old init.d used to source /etc/default/mythtv-backend
> where such localizations could be maintained.
>
> /etc/default/mythtv-backend was subject to about the same amount of
modifications I expect you'll see on the upstart job. Once an a while
maybe, but generally not too often.
--
Mario Limonciello
superm1@xxxxxxxxx
** Changed in: mythbuntu
Status: Triaged => Opinion
** Changed in: mythbuntu
Assignee: Mario Limonciello (superm1) => (unassigned)
--
can't set environment variables in startup
https://bugs.launchpad.net/bugs/668810
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Opinion
Bug description:
Since converting to an upstart job, the mythtv-backend start job is unable to specify environment variables to be set in the mythtv-backend process. The example on hand is proxy setting variables. My backend has to use a proxy in order to use the Internet and now there is no way to tell it short of hacking the upstart job itself, assuming I even understood it's syntax.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mythtv-backend 0.23.1+fixes26732-0ubuntu0+mythbuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
.var.log.mythtv.mythbackend.log: 2010-10-30 13:11:40.330 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min
Architecture: i386
CrashDB: mythbuntu
Date: Sat Oct 30 13:11:54 2010
Installed_mythplugins-dbg: 0.0
Installed_mythtv-dbg: 0.0
ProcEnviron:
PATH=(custom, no user)
LANG=en_CA.utf8
SHELL=/bin/bash
SourcePackage: mythtv
Follow ups
References