Umask broken under Solaris 2.3

Umask broken under Solaris 2.3

Post by ron na » Thu, 30 Dec 1993 08:24:20



Does anyone know of a reason umask fails to work under Solaris 2.3?

Script started on Tue Dec 28 15:21:20 1993
gondor.nash:~> umask 077
gondor.nash:~> touch x
gondor.nash:~> chmod 777 x
gondor.nash:~> cp x y
gondor.nash:~> ls -l x y
-rwxrwxrwx   1 nash     staff          0 Dec 28 15:21 x*
-rwxrwxrwx   1 nash     staff          0 Dec 28 15:21 y*
gondor.nash:~> umask
77
gondor.nash:~> exit

script done on Tue Dec 28 15:21:48 1993

--
             ,--, | Ron Nash      San Diego State University

   ,;`( )__, )  ~ |  
  //  //   '--;   | Gin-N-Tonic   endurance horse
  '   \     |     | Luv on Fire   trusty trail horse

 
 
 

Umask broken under Solaris 2.3

Post by Casper H.S. D » Thu, 30 Dec 1993 09:02:29



>Does anyone know of a reason umask fails to work under Solaris 2.3?
>Script started on Tue Dec 28 15:21:20 1993
>gondor.nash:~> umask 077
>gondor.nash:~> touch x
>gondor.nash:~> chmod 777 x
>gondor.nash:~> cp x y
>gondor.nash:~> ls -l x y
>-rwxrwxrwx   1 nash     staff          0 Dec 28 15:21 x*
>-rwxrwxrwx   1 nash     staff          0 Dec 28 15:21 y*
>gondor.nash:~> umask
>77
>gondor.nash:~> exit
>script done on Tue Dec 28 15:21:48 1993

It isn't ``umask'' that's broken.  It's cp(1) that behaves as
documented.

Of course, you may have gotten used to this behaviour in SunOS 4.1.x,
but even the SunOS 4.1.x cp(1) man page said that cp should use the mode
of the source if the target doesn't exist. The SysV and BSD 4.2
man pages say exactly the same.

Conclusion: SunOS 4.1.x cp(1) is broken, because it doesn't preserve
the mode of the file copied, as stated in the manual page.

What you observe is perfectly normal, documented, UNIX behaviour.

Casper

 
 
 

1. .forward breaks going from Solaris 2.3 to Solaris 2.5

The user account "foo" has a .forward which is the following:

"|cat >> /net/host2/export/home/foo/Archive"

This appends all of foo's mail to Archive which lives in foo's account.
This scheme works great under Solaris 2.3, however it seems to have broken
when mailing from a Solaris 2.5 machine.  Here is the error message
from that 2.5 machine:

   ----- The following addresses had delivery problems -----
"|cat >> /net/host2/export/home/foo/Archive"  (unrecoverable error)
    (expanded from: foo)

   ----- Transcript of session follows -----
550 /home/foo/.forward: line 1: "|cat >> /net/host2/export/home/foo/Archive"...
Address foo is unsafe for mailing to programs

Does anyone know how I can adjust this to work from a 2.5 machine?

Thanks very much,

2. 10/100 generic NIC cards.

3. HELP: Solaris 2.3 <---> Solaris 2.3 PPP link problems

4. Solaris 2.1 Frequently Answered Questions (FAQ) $Revision: 1.15 $

5. HELP: Solaris 2.3 <---> Solaris 2.3 PPP link Problems

6. libpthread causes segfault

7. File manager broken in Solaris 2.3?

8. Forwarding Syslog on Solaris 7

9. X3D-PEX extension broken in Solaris 2.3?

10. Broken lpsched/lpNet on Solaris 2.3 system

11. HP Jetdirect from Solaris 2.3 - Broken HP Product???

12. Solaris 2.3->2.4 broken RPC?

13. Broken lpsched/lpNet on Solaris 2.3 system