mkdir - solaris 10

We are moving to solaris 10, so I have been given the task of validating lots of programs to check that they work.

I have come up with an oddity in a program that is run by root which creates a directory.

Code:

---

mkdir(directory, S_IRWXU | S_IRWXG | S_IRWXO)

---

On a machine running solaris 2.6 it create the directory with the expected permissions of 777 but on the solaris 10 machine it creates it 755, if code amended to do a subsequent call to

Code:

---

chmod(directory, S_IRWXU | S_IRWXG | S_IRWXO)

---

this then works on the solaris 10 machine.

Any idea why mkdir would work differently on solaris 10.

I am new to this, this is my first posting, and any help would be gratefully received.

Cheers.

Sounds like a umask issue:

Quote:

---

NAME
mkdir - create a directory

SYNOPSIS
#include <sys/stat.h>
#include <sys/types.h>

int mkdir(const char *pathname, mode_t mode);

DESCRIPTION
mkdir attempts to create a directory named pathname.

mode specifies the permissions to use. It is modified by the process's
umask in the usual way: the permissions of the created file are (mode &
~umask).

---

The umasks are set differently for root on the different machines, but if umask on solaris 10 machine is changed to be the same in root's .cshrc the problem still occurs.

The code is compiled on a solaris 2.6 machine using gcc 2.95.3

Cheers

I'm wondering, what if you add umask(0); just before the mkdir() call?

We have solved the problem.

The program is run as a daemon via init and apparently prior to Solaris 8 all daemons inherited the umask 0 from init, but in Solaris 8 the default was changed from 0 to 022.

The value can now be set in /etc/default/init (CMASK=value), but we intend to amend the program to fix the problem.

Sorry for not mentioning that the program was being run as a daemon, if this information would have helped.

Cheers