Globbing or not globbing Post: 302708239

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

awk / bash globbing question

I would like to process a list of files matching: GPS*\.xyz with an awk script. I would then like to output the files to GPS*\.xyz.out (e.g. the same file name appended with .out). Something like: awk '{if(NR==1) {offset=-$1}; $1=$1+offset; print }' GPS*.xyz this does exactly what I want EXCEPT...

2. Shell Programming and Scripting

Globbing slash Wildcarding Question

I am on HP-UX and I am trying to come up with a method to call in a list of files named like so. filename020107.dat filename020207.dat filename020307.dat Obviously I can list them ls them like so, ls filename*.dat. In case you did not notice the number is a date and I was hoping to match...

3. Shell Programming and Scripting

globbing, $# is too high after wildcard expansion in bash script

How can I pass in an argument such as "*.k" to a bash script without having to double-quote *.k and not having *.k `glob` to match all files in the pattern? I tried using noglob in my script but this didn't work the way I thought it would.. expansion is still occuring, $# is higher than I...

4. UNIX for Dummies Questions & Answers

File globbing questions

hi guys, jus some file globbing questions sed "s/^.*on//" what does the full stop and asterisk means? i onli know that ^ means inverse or not

5. Shell Programming and Scripting

Negation in Bash Globbing

$ ls -1 a.1 b.1 x_a.1 x_b.1 $ ls -1 * b.1 x_a.1 x_b.1 $ ls -1 ** a.1 b.1 x_a.1 x_b.1The last result is not as expected. Why? Thanks.

6. Shell Programming and Scripting

File globbing order

Hi , I'm facing a different behaviour with one of my shell script for last few days. It was working good before that. here is my code for the script FileRemove.sh #get the file name# file1=$1 file2=$2 rm $file1 # delete the old file mv $file2 <target path> #move the new file to the target...

LEARN ABOUT SUSE

chsh

chsh(1) 						      General Commands Manual							   chsh(1)

NAME

       chsh - change login shell

SYNOPSIS

       chsh [-D binddn] [-P path] [-s shell] [-l] [-q] [-u] [-v] [user]

DESCRIPTION

       chsh  is  used  to  change  the	user login shell.  A normal user may only change the login shell for their own account, the super user may
       change the login shell for any account.

       If a shell is not given on the command line, chsh operates in an interactive fashion, prompting the user  with  the  current  login  shell.
       Enter  the  new	value  to change the field, or leave the line blank to use the current value. Enter none to remove the current value.  The
       current value is displayed between a pair of [ ] marks.

       The only restrictions placed on the login shell is that the command name must be listed in /etc/shells, unless the invoker  is  the  super-
       user, and then any value may be added.  An account with a restricted login shell may not change their login shell.

       This version of chsh is able to change the shell of local, NIS, NIS+ and LDAP accounts , if the permissions allow it.

OPTIONS

       -D, --binddn binddn
	      Use  the	Distinguished  Name binddn to bind to the LDAP directory.  The user will be prompted for a password for simple authentica-
	      tion.

       -P, --path path
	      The passwd file is located below the specified directory path. chsh will use this files, not /etc/passwd.  This is useful for  exam-
	      ple  on  NIS master servers, where you do not want to give all users in the NIS database automatic access to your NIS server and the
	      NIS map is build from special files.

       -s, --shell
	      Specify your login shell.

       -l, --list-shells
	      Print the list of shells listed in /etc/shells and exit.

       -q, --quite
	      Don't be verbose.

       -u, --usage
	      Print a usage message and exit.

	   --help
	      Print a more verbose help text and exit.

       -v, --version
	      Print version information and exit.

FILES

       /etc/passwd - user account information
       /etc/shells - list of valid login shells

SEE ALSO

       chfn(1), passwd(5), shells(5)

AUTHOR

       Thorsten Kukuk <kukuk@suse.de>

pwdutils							   February 2004							   chsh(1)