Umask strange behaviour 555=444 ?

Why is umaks 654 and 644 returning the same file permission?

# umask 555
# touch t1
total 0
--w--w--w- 1 root root 0 2007-05-16 05:28 t1

I think that t1 should be --- --- --- (000) since --x --x --x (111)
would not be allowed for common files (just directories).

Moreover, why would umaks 555 produce the same result as umask 444 ??

.

Relevant Pages

  • Re: Umask strange behaviour 555=444 ?
    ... would not be allowed for common files. ... why would umaks 555 produce the same result as umask 444 ?? ... Robert Riches ...
    (comp.os.linux.misc)
  • Re: what is umask?
    ... > Dear Member what is umask? ... umask identifies which file permission bits you /don't/ ... If a program sets those bits, ... Lew Pitcher, IT Specialist, Enterprise Data Systems ...
    (comp.os.linux.misc)
  • Re: function umask() and problem in GD::image->png
    ... I saw some code put "umask 022;" in the near beginning of perl ... script, after execution, the file permission is not changed to 002. ...
    (perl.beginners)
  • Setting Default File Permissions on Server for Use with Secure FTP
    ... When users transfer files to the server using Secure FTP, ... the default file permission when using SFTP set to '755'. ... to 'umask 022'. ... Placing 'umask 022' in /etc/ssh2/ssh2_config ...
    (comp.security.ssh)
  • Re: what is umask?
    ... > Dear Member what is umask? ... > and what is the relationship between umask and the file permission ...
    (comp.os.linux.misc)