[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/67141
Title:
Please cre
komputes: They aren't in the init scripts, etc.
The problem is that if a user adds GREP_OPTIONS to their environment
(manually, or via .bashrc, etc.) then it can break init.d scripts, etc.
At the time, if you did `env GREP_OPTIONS=-E /etc/init.d/blah start` it
could break the `blah` script in unp
In attempting to triage this bug, I'm unable to find GREP_OPTIONS in env
command output or in my .bashrc. Is this still an issue in the latest
release, if so can you specify where this variable can be found after a
default installation.
** Changed in: ubuntu
Status: New => Incomplete
--
Y
** This bug is no longer a duplicate of bug 75031
GREP_OPTIONS is evil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/67141
Title:
Please create and enforce a system-wide policy to unset GREP_OPTI
*** This bug is a duplicate of bug 75031 ***
https://bugs.launchpad.net/bugs/75031
I do not understand why this is marked as duplicate of bug #75031.
bug #75031 is about the mysql init.d script choking on a poorly set
GREP_OPTION.
bug #67141 (this bug) is about a system-wide policy to unset
*** This bug is a duplicate of bug 75031 ***
https://bugs.launchpad.net/bugs/75031
** This bug has been marked a duplicate of bug 75031
GREP_OPTIONS is evil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I'm not asking to remove GREP_OPTIONS from grep. I'm saying that in
system scripts, such as the stuff in /etc/init.d/*, should some how
ignore GREP_OPTIONS. I broke scripts by setting GREP_OPTIONS in non-
obvious ways.
It's really hard to track down these problems, so maybe we should unset
them
GREP_OPTIONS is useful, because it allows the user set one option for
many forms of grep (grep, egrep, fgrep, rgrep, zgrep, bzgrep, bzfgrep,
bzegrep, etc.).
For example, here's what the man page for bzgrep says:
If the GREP environment variable is set, bzgrep uses it as the grep
program to be
** Package changed: grep (Ubuntu) => ubuntu
--
Please create and enforce a system-wide policy to unset GREP_OPTION by default
https://bugs.launchpad.net/bugs/67141
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
i think this bug should not be reported against grep but against ubuntu,
if that is possible. i tried to do that but i failed.
just for reference, here is a list of bug reports about problems caused by
GREP_OPTIONS:
bug #75031
bug #257984
bug #398393
bug #540733
also related:
bug #545675
and fo
10 matches
Mail list logo
