Hi,
On Fri, 07 Jul 2006 Will Beldman wrote:
> 1. I have explained how I got long filenames (From another message):
> "I don't own the files. One example is 259 characters long. They are
> caused by users who have chosen to name their files the same thing as
> the first sentence of their MS Word
On 7/7/06, Linda Walsh wrote:
It is quite trivial. He's prepending either "S:/" or
"/cygdrive/s" to an existing pathname. The existing pathname can be at the
limit (~256 bytes). Adding either prefix, above, the pathlen becomes 259
...which is why MAX_PATH on windows is 260, to allow
On 7/7/06, Dave Korn wrote:
I *still* don't understand how it is possible for your users to
create files with names that are longer than the maximum filename length that
windows permits - this is a limitation of the windows OS and filing system,
not one that cygwin imposes.
Dave:
Probably the
1. I have explained how I got long filenames (From another message):
"I don't own the files. One example is 259 characters long. They are
caused by users who have chosen to name their files the same thing as
the first sentence of their MS Word doc."
2. Most of the text you have quoted was my fir
Dave Korn wrote:
Still lacking in useful information. You *still* haven't told us HOW on
earth you managed to get impossibly long file names, you *still* haven't shown
us the names of any directories that have failed.
---
It is quite trivial. He's prepending either "S:/" or
"/cygdriv
On 07 July 2006 17:03, Brian Dessent wrote:
> Dave Korn wrote:
>
>> filenames. I *still* don't understand how it is possible for your users to
>> create files with names that are longer than the maximum filename length
>> that windows permits - this is a limitation of the windows OS and filing
>
Dave Korn wrote:
> filenames. I *still* don't understand how it is possible for your users to
> create files with names that are longer than the maximum filename length that
> windows permits - this is a limitation of the windows OS and filing system,
> not one that cygwin imposes.
As far as I r
On 07 July 2006 15:38, Will Beldman wrote:
> The problem is still here.
>
> As a refresher, here's the original problem:
> ===
Still lacking in useful information. You *still* haven't told us HOW on
earth you managed to get impossibly long file names, you *still* haven
Will Beldman wrote:
Can anyone tell me under what circumstance the message
du: fts_read failed: Permission denied
would come up. I should be able to troubleshoot things from there if
only I knew what that error message is really complaining about.
When all else fails, you can try reading the s
The problem is still here.
As a refresher, here's the original problem:
===
I need to determine disk usage for each directory on a Microsoft cluster
server. As a linux junkie, du is *the* tool for automating this kind of
stuff so I installed cygwin, mapped some drives an
On 7/4/06, Will Beldman wrote:
I will try to run the script against /cygdrive/s/* instead of S:/* and
let you all know if it fails.
You still haven't posted the actual command line you are using, but
why not use /cygdrive/s instead of /cygdrive/s/* , which should avoid
the need for quoting?
--
I will try to run the script against /cygdrive/s/* instead of S:/* and
let you all know if it fails.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Lev Bishop wrote:
On 7/3/06, Larry Hall (Cygwin) wrote:
Use POSIX paths (i.e. /cygdrive/s). Here I think you've found an
application
for 'find'. How about something like:
find /cygdrive/s -maxdepth 1 -print0 | xargs -0 du
How is that better than:
du /cygdrive/s
?
The OP claimed to have
On 7/3/06, Larry Hall (Cygwin) wrote:
Use POSIX paths (i.e. /cygdrive/s). Here I think you've found an application
for 'find'. How about something like:
find /cygdrive/s -maxdepth 1 -print0 | xargs -0 du
How is that better than:
du /cygdrive/s
?
L
--
Unsubscribe info: http://cygwin.co
Will Beldman wrote:
> In reply to:
>> On 03 July 2006 14:50, Will Beldman wrote:
>>
>> I need to determine disk usage for each directory on a Microsoft
cluster
>> server. As a linux junkie, du is *the* tool for automating this kind of
>> stuff so I installed cygwin, mapped some drives an
> In reply to:
>> On 03 July 2006 14:50, Will Beldman wrote:
>>
>> I need to determine disk usage for each directory on a Microsoft cluster
>> server. As a linux junkie, du is *the* tool for automating this kind of
>> stuff so I installed cygwin, mapped some drives and tried to schedule
>> the ut
On 03 July 2006 14:50, Will Beldman wrote:
> I need to determine disk usage for each directory on a Microsoft cluster
> server. As a linux junkie, du is *the* tool for automating this kind of
> stuff so I installed cygwin, mapped some drives and tried to schedule
> the utility to run at night. How
17 matches
Mail list logo
