summaryrefslogtreecommitdiffstats
path: root/usr.bin/env
Commit message (Collapse)AuthorAgeFilesLines
* Build usr.bin/ with WARNS=6 by default.ed2010-01-021-1/+0
| | | | Also add some missing $FreeBSD$ to keep svn happy.
* Update the date on the man-page to reflect the date that the '-u name'gad2008-05-061-1/+1
| | | | change was committed, instead of when I had first started writing it...
* Add the '-u name' option to the env command, which will completely unsetgad2008-04-172-8/+31
| | | | | | | | the given variable name (removing it from the environment, instead of just setting it to a null value). PR: bin/65649 MFC after: 2 weeks
* Significantly reduce the memory leak as noted in BUGS section forscf2007-07-041-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | setenv(3) by tracking the size of the memory allocated instead of using strlen() on the current value. Convert all calls to POSIX from historic BSD API: - unsetenv returns an int. - putenv takes a char * instead of const char *. - putenv no longer makes a copy of the input string. - errno is set appropriately for POSIX. Exceptions involve bad environ variable and internal initialization code. These both set errno to EFAULT. Several patches to base utilities to handle the POSIX changes from Andrey Chernov's previous commit. A few I re-wrote to use setenv() instead of putenv(). New regression module for tools/regression/environ to test these functions. It also can be used to test the performance. Bump __FreeBSD_version to 700050 due to API change. PR: kern/99826 Approved by: wes Approved by: re (kensmith)
* Back out all POSIXified *env() changes.ache2007-05-011-3/+3
| | | | | | | | | Not because I admit they are technically wrong and not because of bug reports (I receive nothing). But because I surprisingly meets so strong opposition and resistance so lost any desire to continue that. Anyone who interested in POSIX can dig out what changes and how through cvs diffs.
* env calls setenv("name=value", "value", 1); which violates POSIX:ache2007-04-301-3/+3
| | | | | | | "The setenv( ) function shall fail if: [EINVAL] The name argument is a null pointer, points to an empty string, or points to a string containing an '=' character." The fix (like all others in this subject) is backward-compatible.
* Fix minor memory leak when expanding ${variable}sgad2005-07-181-1/+5
| | | | | Noticed by: Dave Hart MFC plans: after checking with re@
* Fix two minor parsing bugs in -S processing:gad2005-07-131-14/+23
| | | | | | | | | | | 1) An unquoted space is always a separator, even when not "in_arg". 2) When a new destination buffer must be allocated during variable substitution, only copy data from the active buffer to the new one when we *are* "in_arg". These were noticed when testing variable-substitution of variables which have null values, and are not inside quoted strings... MFC plans: after a few days, and re@ approval...
* Tidy up the markup.ru2005-06-221-34/+49
| | | | | Approved by: re (blanket) OK'ed by: gad
* Fix a bug where the value of ${SOMEVAR} would simply disappear if theregad2005-06-211-23/+48
| | | | | | | | was a separator character immediately before it. This wasn't likely to happen in #-lines, but we might as well get it right. Also fix it so that "" and "" will create a zero-length argument. Approved by: re (blanket `env')
* Put in a more descriptive heading for the `env' command.gad2005-06-211-1/+1
| | | | | Noticed by: Matthew D Fuller Approved by: re (blanket `env')
* Undo r1.14 to env.c. While it is unusual for environment variables togad2005-06-212-7/+2
| | | | | | | | start with a '/', they are more supported (by POSIX and SUSv3) than filenames which have an '=' in them. Noticed by: tjr Approved by: re (blanket `env')
* Add the '-S' and '-P' options. The '-S' option can be used to splitgad2005-06-205-32/+829
| | | | | | | | | | | | | | apart a string, and supports some text substitutions. This can be used to provide all the flexibility (and more!) that was lost by recent changes to how the kernel parses #!-lines in shell scripts. The '-P' option provides a way to specify an alternate set of directories to use when searching for the 'utility' program to run. This way you can be sure what directories are used for that search, without changing the value of PATH that the user has set. Note that on FreeBSD 6.0, this option is worthless unless the '-S' option is also used. Approved by: re (blanket `env')
* If the `utility' specified starts with a '/' character, then execute itgad2005-06-201-1/+2
| | | | | | | without checking it for an equals-sign. If it starts with a slash, then it cannot be a request to set the value of a valid environment variable. Approved by: re (blanket `env')
* Move the code that clears the environment when `-i' is specified, so it thatgad2005-06-201-5/+9
| | | | | | | it does not happen until all single-letter options are processed. This will be important for the -S option, which will be coming soon. Approved by: re (blanket `env')
* Add a '-v' option to `env', to make it easier to discover exactly what stepsgad2005-06-201-4/+25
| | | | | | | it is doing, and what order it does them. This will be much more useful as more options are added. Approved by: re (blanket `env')
* Added the EXIT STATUS section where appropriate.ru2005-01-171-1/+1
|
* Language and markup polishing.ru2004-05-191-11/+14
|
* Fix grammar bogon.schweikh2004-02-291-1/+1
|
* Removed (after the env(1)/printenv(1) split) extraneous argumentsru2003-11-021-9/+9
| | | | to the .Nm macro.
* Split the env(1) manpage off from printenv(1); there is not much pointtjr2003-06-012-1/+144
| | | | in keeping them together. Mention that printenv is obsolescent.
* ANSIify function definitions.dwmalone2002-09-041-4/+2
| | | | | | | | | Add some constness to avoid some warnings. Remove use register keyword. Deal with missing/unneeded extern/prototypes. Some minor type changes/casts to avoid warnings. Reviewed by: md5
* Discourage use of env(1)'s "-" flag by moving its description to thetjr2002-06-281-1/+1
| | | | Compatibility section of the manual page.
* Indicate that env(1) allows you to supply arguments to the utility ittjr2002-06-191-1/+1
| | | | | | | | | | executes in the usage() message and manual page. Use "utility" instead of "command" in both places to emphasise that shell builtins etc. will not work, and to be consistent with the terminology used by POSIX. PR: 39210 Submitted by: Danny J. Zerkel <dzerkel@columbus.rr.com> MFC after: 1 week
* remove __Pimp2002-03-221-1/+1
|
* Leave the `copyright' variable exposed, since the main purpose of itmike2002-03-071-2/+2
| | | | | | is to put a copyright in the object file. Submitted by: bde
* Use new ID scheme.mike2002-02-211-3/+9
| | | | | | | Fix env(1)'s exit status to conform with SUSv3. Submitted by: Tim Robbins <tim@robbins.dropbear.id.au> MFC after: 2 weeks
* Remove leaf node WARNS?=2 (that mainly I added). This shouldmarkm2002-02-081-1/+0
| | | | help the GCC3 transition and CURRENT in general.
* Set WARNS=2 on programs that compile cleanly with it; add $FreeBSD$dd2001-06-301-2/+3
| | | | | | where necessary. Submitted by: Mike Barcroft <mike@q9media.com>
* Add ``-i'' option, which is the same as ``-''. The -i option is thesheldonh1999-08-271-2/+3
| | | | | | | | | recommended option in the manpage, but the - option remains for backward compatibility and is documented as such. PR: 13363 Reported by: James Howard <howardjp@wam.umd.edu> Reviewed by: bde
* Tweaks to allow compiling -Wall (mostly adding "const" to char rcsid[]).archie1998-12-062-2/+3
|
* Add usage().charnier1997-06-301-3/+11
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-272-0/+88
OpenPOWER on IntegriCloud