bash script to create folders including making recursive folders....
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think 'getopt' command is what you're looking for. If '-newclientname' is of the type '-newclientname=XXX' then you need to parse XXX out before using it.
sorry i thought about that exact thing the moment i shut my pc down last night. catkin, you are correct this is what i am after. where XX would be passed in at time of running script, or even a prompt.
I think 'getopt' command is what you're looking for. If '-newclientname' is of the type '-newclientname=XXX' then you need to parse XXX out before using it.
getopt is probably fine too, but to simplify matters, why not just pass the clientname as the argument to the script? Like:
shell$ ./script john
for client john? And if $1 happens to be empty when the script error-checks for the clientname, exit with an error message (and of course, make sure john doesn't already exist too!)
Last edited by GrapefruiTgirl; 11-28-2009 at 01:02 AM.
ive had a though, i might aswell just do, mkdir 7 times. was trying to be to clever, but the definition of clever is to realise that there may be a better way of doing something, but if it takes longer than the simpler version to get working and achieves the same thing...
silly me. ive got exactly what i need now anyway. momment of madness. sorry for the stupid post. thanks for the help.
sorry i thought about that exact thing the moment i shut my pc down last night. catkin, you are correct this is what i am after. where XX would be passed in at time of running script, or even a prompt.
thanks ( sorry for the confusion )
GrapefruiTgirl's suggestion regards the script sounds good so
Code:
#!/bin/bash
[[ $# -ne 1 || "$1" == '' ]] && echo "Usage: ${0##*/} client_name" >&2 && \exit 1
CLIENT_NAME="$1"
dirs=( $( echo /srv/store/nearling-storage/clients/$CLIENT_NAME/{audio,graphics,file,test/{test-staging,TEST-EXPORT},test1/{gra,aud}} ) )
for dir in ${dirs[@]}
do
if [[ -e "$dir" ]]; then
echo "$dir exists!" >&2
\exit 1
else
mkdir -p "$dir"
[[ $? -ne 0 ]] && \exit 1
echo "Created directory $dir"
fi
done
This will fail if the client name includes embedded whitespace such as a space character.
ive had a though, i might aswell just do, mkdir 7 times. was trying to be to clever, but the definition of clever is to realise that there may be a better way of doing something, but if it takes longer than the simpler version to get working and achieves the same thing...
Truly there is a pragmatic trade-off between the perfect and how long it takes to achieve! But it's good to trap and report errors and that would mean a lot of coding for 7 separate mkdirs. And it's good to push the envelope a bit, learning more of bash's features (until the point of forgetting them faster than learning them!).
Thanks for making me learn about the {<string>[,<string> ...]} technique -- it's useful but I have never used it
Thanks for making me learn about the {<string>[,<string> ...]} technique -- it's useful but I have never used it
Me neither -- first time I have looked at it is right here AFAIK. Thanks catkin!
I was in the process of making a simple sed to replace any spaces with underscores, but then realized this would mean other (unnecessary and excessive) mods to catkins script, to grab >1 words given as a client_name and make them one name. If the OP wishes for this, it wouldn't be too hard, but as it stands, this looks adequate
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
