- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Very Unusual ftp dir get and mget results
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 11:44 AM
тАО12-13-2002 11:44 AM
Very Unusual ftp dir get and mget results
cd to "incoming" directory.
dir shows two files.
ap.husbaan100.inbound.0212121548
ap.husbaan140.inbound.0212121548
dir ap* (shows no files.)
dir *inbound* (shows no files.)
dir *100* (shows only the first file.)
dir *140* (shows only the second file.)
dir *0212* (shows both files.)
get ap.husbaan140.inbound.0212121548 (works)
ftp> mget * (does not work)
mget *? y
Error opening local file *.
> *:Invalid argument
In summary, numeric matching seems to work, but not alpha.
mget does not want to work no matter what.
get seems to work OK.
What is going on here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 11:53 AM
тАО12-13-2002 11:53 AM
Re: Very Unusual ftp dir get and mget results
Sounds like file name globbing is disabled by default.
At an ftp> prompt enter
glob
and then try your wildcards again.
HTH,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 12:10 PM
тАО12-13-2002 12:10 PM
Re: Very Unusual ftp dir get and mget results
Since my initial post, I discovered that UPPER CASE letters would match.
dir AP* (shows both files)
mget AP* (will get both)
My guess is that the files are stored as upper case and ftp is mapping to lower case before displaying results to me.
Does this sound possible?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 12:26 PM
тАО12-13-2002 12:26 PM
Re: Very Unusual ftp dir get and mget results
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 12:30 PM
тАО12-13-2002 12:30 PM
Re: Very Unusual ftp dir get and mget results
I don't think it's translating - it's just being literal.
You can try
ftp> case
to get the server to switch cases & test the wildcards on the mget command.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 01:12 PM
тАО12-13-2002 01:12 PM