Random chmod errors

Hello friends, some of my users are encountering random errors with the chmod command. The errors are not exactly reproducible, so I cannot even narrow down the circumstances of their occurrance. What else do I know: - Following message occurs: chmod: changing permissions of `filename'

Re: Random chmod errors

On Wed, Jun 08, 2005 at 05:33:59PM +0200, Peter Kratzer wrote: Hello friends, some of my users are encountering random errors with the chmod command. The errors are not exactly reproducible, so I cannot even narrow down the circumstances of their occurrance. - What operating systems are

Re: Random chmod errors

James Youngman [EMAIL PROTECTED] wrote on 2005-06-08 18:01:26: On Wed, Jun 08, 2005 at 05:33:59PM +0200, Peter Kratzer wrote: Hello friends, some of my users are encountering random errors with the chmod command. The errors are not exactly reproducible, so I cannot even narrow down the

PATCH: adds seq ordinal/hexidecimal integer output

seq offers -f to output floating point output. Includes is a patch to add ordinal and hexidecimal output. Output is cast to int first. Also, the manual page still needs updated, I believe. I'd like to change this to output 64-bit numbers, not just 32-bit, though I'm not sure how--coreutils'

Re: Random chmod errors

Peter Kratzer wrote: some of my users are encountering random errors with the chmod command. The errors are not exactly reproducible, so I cannot even narrow down the circumstances of their occurrance. Problems like that can be disheartening and hard to track down. I saw James' question and

Re: Suggested enhancement to du command - show last modified date.

The following patch is my fist iteration at implementing my suggested --last-modified option for du. It is a simple port of my original draft code to the latest CVS source for du. Doesn't the standard ISO-8601 date format accomplish that, too? I have changed the default date format to be

Re: Suggested enhancement to du command - show last modified date.

Thanks for contributing! Some comments: Internally, file time stamps should be maintained to nanosecond resolution, not just 1-second resolution. As far as the --last-modified option syntax goes, I suggest that we use a syntax that is more like that of touch --time. E.g., du

Re: PATCH: adds seq ordinal/hexidecimal integer output

Kuwanger [EMAIL PROTECTED] writes: seq offers -f to output floating point output. Includes is a patch to add ordinal and hexidecimal output. Output is cast to int first. It should be cast to uintmax_t, no? Also, the manual page still needs updated, I believe. Yes. That's usually the

Re: Random chmod errors

Peter Kratzer [EMAIL PROTECTED] writes: They are using NFS (NAS filer). Possibly you're running into ACL problems. Are there any ACLs in use anywhere on that file system? If so, that can prevent the chmod system call from succeeding, and this will cause the chmod command to fail as well. If

Re: PATCH: adds seq [octal]/hexidecimal integer output

On Wednesday 08 June 2005 02:46 pm, Paul Eggert wrote: Kuwanger [EMAIL PROTECTED] writes: seq offers -f to output floating point output. Includes is a patch to add [octal] and hexidecimal output. Output is cast to int first. It should be cast to uintmax_t, no? Though I'm not entirely

flag for one second timestamp comparison granularity

Perhaps add a flag to cp, find, etc. to reduce time comparisons to only one second granularity, as depending on the device mounted, or if we have since rebooted, times that should be the same can be reported back differently by the operating system. Or at least add a warning on man and Info