On Thu, 17 Feb 2005, Martin L. Sage wrote:
>> When I boot in Linux i686 2.6.10-gentoo-r4 I get a number of error
>> messages that state that various environment variables exported from
>> /var/lib/init.d/envcache are readonly variables. The include
>> BASH_VERSINFO, EUID, SHELLOPTS, PPID, and UID.
These are readonly variables. Why are they in your
/var/lib/init.d/envcache? They're certainly not in my
/var/lib/init.d/envcache, on any of my systems.
Look in /etc/env.d for files which contain these variables, and find out
why it has them listed in it. (You can use grep -l EUID /etc/env.d/*,
for example, to locate said files.)
>> In addition when I logon as "root" or some other user i get several
>> message preceeded by "-bash:" They are
>>
>> -bash: BASH_VERSINFO: readonly variable
>> -bash: EUID: readonly variable
>> -bash: /etc/profile.env: line 46: syntax error near unexpected token `('
>> -bash: /etc/profile.env: line 46: `export
>> BASH_VERSION=''2.05b.0(1)-release'''
My main system's /etc/profile.env does not have 46 lines. It only
defines INFODIR, INFOPATH, CONFIG_PROTECT_MASK, ROOTPATH,
CONFIG_PROTECT, MANPATH, PATH, LESS, HOSTNAME, G_BROKEN_FILENAMES,
GCC_SPECS, LESSOPEN, CVS_RSH, PAGER, PYTHONDOCS, and RSYNC_RSH.
Admittedly, 'tis a pretty minimal system. My dev box has a few more
lines, but it's only at 30. This is, of course, not to say that you
clearly have too many, but it is suggestive that someone or something
has been indiscriminately adding stuff - especially as you have five
that should *not* be there.
>> As near as I can tell everything works properly.
Of course it will. Attempting to write to a readonly variable will
produce an error, nothing more. So you're not actually breaking
anything with having those constants in there as variables.
Ed
--
[email protected] mailing list
