Sponsored Content
Top Forums Shell Programming and Scripting Using links with wildcards in bash. Post 302352881 by Annihilannic on Monday 14th of September 2009 02:26:30 AM
Old 09-14-2009
I that seems normal when there are no files that match the first parameter, so you should probably test for their existence before attemping to symlink.

Personally I'd stick with the for loop since it's safer and more portable.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Wildcards in VI

I'm trying to delete lines from a large text file using VI. Every line that I am wanting to delete start with 'S' - all others do not. (A list of users) I've tried using * but doesn't seem to like it...any ideas... Doesn't have to be VI - but I'm better with VI than sed/awk. (8 Replies)
Discussion started by: peter.herlihy
8 Replies

2. UNIX for Dummies Questions & Answers

wildcards

when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies

3. UNIX for Dummies Questions & Answers

ls with wildcards

ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this ls s*.dat > file_names.txt can't figure out whats wrong with that line, any ideas? thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies

4. Shell Programming and Scripting

Symbolic Links - BASH Script

Hi all, This is my first message in this forum. I'd like to know if there is a nice way to get the complete path from a symbolic link. Example: When I do a ls -ltr I see this output. lrwxr-xr-x 1 mmmm users 66 Sep 4 09:58 LINK_SEND ->... (4 Replies)
Discussion started by: rodrimuino
4 Replies

5. UNIX for Dummies Questions & Answers

wildcards NOT

Hi All Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines. tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies

6. UNIX for Advanced & Expert Users

Wildcards

These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all. GNU/Linux Command-Line Tools Guide - Wildcards GREP (1 Reply)
Discussion started by: cokedude
1 Replies

7. Solaris

Hard Links and Soft or Sym links

When loooking at files in a directory using ls, how can I tell if I have a hard link or soft link? (11 Replies)
Discussion started by: Harleyrci
11 Replies

8. AIX

List all the soft links and hard links

Hi I'm logged in as root in an aix box Which command will list all the soft links and hard links present in the server ? (2 Replies)
Discussion started by: newtoaixos
2 Replies
NSEND(1)							       nsend								  NSEND(1)

NAME
nsend - Send messages to users or groups SYNOPSIS
nsend [ -h ] [ -S server ] [ -U user name ] [ -P password | -n ] [ -C ] [ -a ] -i objectID | -c connNum[,...] | { [ -t recipient type ] -o recipient name | recipient name } message DESCRIPTION
With nsend, you can send messages to the user's workstations. nsend looks up the file $HOME/.nwclient to find a file server, a user name and possibly a password. See nwclient(5) for more information. Please note that the access permissions of .nwclient MUST be 0600, for security reasons. OPTIONS
recipient name recipient name is either the NetWare name of the user to receive the message or the name of an existing user group on that server. You can use wildcards in this specification. -o recipient name Specifies recipient's name. This can specify user or group. -t recipent type Specifies recipient's type. -c connNum[,...] Specifies connection numbers of recipients. You can use this option as workaround to deliver messages to directory services users. -i userID Specifies recipient's object ID. You can use this option as workaround to deliver messages to directory services users. message message is the message to be sent. Please note that this has to be a single command line argument. If you want to send a message that contains spaces, you have to quote them on the command line. For example, to annoy your system administrator, you should try nsend supervisor 'I know how this works!' Program first searches (wildcards allowed) bindery with recipients name and type. If user is found, message is sent to this user, if group is found, message is sent to this group. Other object types are ignored. If no suitable object was found in this phase, connection list for specified object is retrieved (no wildcards allowed) and message is sent to this object (including print servers and so on). No expansions on group is done this time. -a By default, nsend prepends 'From ....' text to message. You can suppress this by adding -a to command line. -S server server is the name of the server you want to use. -U user name If the user name your NetWare administrator gave to you differs from your unix user-id, you should use -U to tell the server about your NetWare user name. -P password You may want to give the password required by the server on the command line. You should be careful about using passwords in scripts. -n -n should be given if specified user does not have password. If neither -n nor -P are given, nsend prompts for a password. -C By default, passwords are converted to uppercase before they are sent to the server, because most servers require this. You can turn off this conversion by -C. BUGS
Directory services connection are not supported yet. Options -c, -i and -o cannot be used together. If user is specified multiple times (using wildcards in group specification or by repeating same number in -c), message is delivered multi- ple times to him. SEE ALSO
nwclient(5), nprint(1), slist(1), ncpmount(8), ncpumount(8) CREDITS
nsend was written by looking at mars_nwe's message handling. Thanks to Martin Stover <mstover@freeway.de>. Support for Netware groups by Philippe Andersson <philippe_andersson@ste.scitex.com>. Support for connections greater than 255 by Petr Vandrovec <vandrove@vc.cvut.cz>. nsend 04/07/1999 NSEND(1)
All times are GMT -4. The time now is 03:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy