I take it the program actually executes the chmod after it finishes writing ?
> Oh, and I also get gazillions of:
>
> kernel: nfs_free_dentries: found log/syslog, d_count=1, hashed=0
> kernel: __nfs_fhget: inode 118790 still busy, i_count
> kernel: __nfs_fhget: killing log/syslog filehandle
> kernel: nfs_revalidate_inode: log/syslog getattr failed, ino=118790, error=-70
Nod. Folks are gradually stamping on all of these
> kernel: NFS: bad fh 0000000000000000000000000000000000000000000000000000000000000000
> kernel: c0f383a00001d0060001d0010000080900000809000000020000000000000000
That is bad. Something got a bad handle.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/