[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in /etc/profile.d/lilypond.sh (with fix!)

From: Reuben Thomas
Subject: Re: Bug in /etc/profile.d/lilypond.sh (with fix!)
Date: Thu, 4 Dec 2003 13:17:06 +0100 (CET)

On Thu, 4 Dec 2003, Jan Nieuwenhuizen wrote:

> Reuben Thomas <address@hidden> writes:
> >> But only if you start a second login shell, and you shouldn't be doing 
> >> that.
> >
> > Sadly I don't have to do that. RedHat in their infinite wisdom run the
> > scripts in /etc/profile.d from /etc/bashrc if they haven't already been
> > run by /etc/profile.
> They must be very wise at Red Hat, but this smells like a
> configuration bug, sort of.  The bash manual promises to run
> '{/etc/,~/.bash_,~/.}profile' only upon login.
> Are you sure that you did not make this change yourself?


$ rpm -qf /etc/bashrc
$ rpm -V setup
S.5....T c /etc/printcap
..?..... c /etc/securetty

i.e. my /etc/bashrc file is as supplied in the RPM.

> > I presume they have at least a plausible reason,
> > since it's a sin of comission rather than of omission!
> Probably.  I'm not thrilled by Red Hat's concept of fixing stuff in
> /etc/profile.d/* anyway.

FWIW I've filed a bug report in RedHat's Bugzilla (although I put it as
more of a question than a bug report). I first googled extensively and
looked in the RedHat manuals to try to find an (official)  justification
of this behaviour, but couldn't find one.

L'art des vers est de transformer en beaut├ęs les faiblesses (Aragon)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]