[SERVER-2446] mongodump does not indicate it cannot write to a dump file on Windows Created: 31/Jan/11 Updated: 29/Feb/12 Resolved: 31/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 1.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Justin Dearing | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 32 bit |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
If I open a command prompt as an unprivileged user and cd to c:\windows bsondump will not output an error that it cannot write anything. It will output as if nothing has gone wrong: C:\Users\DearingJ>cd \Windows C:\Windows>mongodump C:\Windows>dir dump Directory of C:\Windows File Not Found C:\Windows> |
| Comments |
| Comment by Spencer Brody (Inactive) [ 11/Oct/11 ] |
|
Just tested this in 2.0 and I believe the problem has been fixed. I see: error: boost::filesystem::create_directory: Access is denied: "dump" |