inetd start error ..

[someone_4]

I decided to start another post on my inetd error.

/sbin/init.d/inetd start
Internet Services started

/sbin/init.d/inetd[53]: umask: The specified number is not valid for this comman
d.

It is rather odd. I check /etc/inetd.conf and I dont have any odd umask. So I looked at /sbin/init.d/inetd

And the start part of the script has something about a umask.

'start')
if [ -f /etc/rc.config ]; then
. /etc/rc.config
else
echo "ERROR: /etc/rc.config defaults file MISSING"
fi

mask=`umask`
umask 000

[ -x /usr/sbin/inetd ] && /usr/sbin/inetd $INETD_ARGS
set_return
if [ $rval -eq 0 ]; then
echo "Internet Services started"
else
echo "Unable to start Internet Services"
fi

umask $mask
;;

But that is the same as it is on other servers.

The difference is that on the server that I am getting the error on ..

#umask
07077

#umask -S
u=rwx,g=,o=


on the other

#umask
00

# umask -S
u=rwx,g=rwx,o=rwx

looks like something somewhere is setting that umask that is could probably be making that start up script to fail .. Am I on the right track?

Richard

[Jeff Schussele]

Like a bloodhound my man.

Jeff

[Sridhar Bhaskarla]

Richard,

This is resulting from the 53rd line of inetd startup script.

53rd line is exactly umask $mask

mask is getting initialized on line 42 with the command "umask"

So, check your /etc/profile or your .profile or root's .profile to see if you are setting a wrong umask.

Correct it if so.

-Sri

[Sanjay_6]

Hi Richard,

Check your /etc/inetd.conf file and see if you have defined an invalid umsak with any of the daemon.

Hope this help.

Regds

[Michael Tully]

umsak??

Must be a new built in shell variable....

[SHABU KHAN · Accepted solution]

Richard,

This thread should help:

http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0x39bb854994d9d4118fef0090279cd0f9,00.html

Look for Steven's suggestion..

-Shabu

[K.Vijayaragavan.]

Check the umask value set at "/sbin/rc"

"cat /sbin/rc | grep umask"


-K.Vijay

[someone_4]

From the link to the other post here is the problem. But does anyone know why this is for security reason?

Steven Sim Kok Leong:
Hi,

Did you recently enabled trusted systems (TCB)? I ever encountered this symptom after I convert the system from untrusted to trusted . For security reasons, TCB set the default umask to 07077. To overcome the default umask, you need to specify your umask settings in /etc/profile eg. umask 022

[Michael Tully]

Richard,

Just as a caveat to this post, always make a habit of setting the umask in /etc/profile to:

umask 022

when the building the system is the best time. This will avoid many problems later on by the system creating oodles of files with inappropriate permissions like 666 and ownded by root.

Michael