chown : not owner !!!

Apparantly, you cant do a chown in Solaris. Here’s more…

http://unix.derkeiler.com/Newsgroups/comp.unix.solaris/2004-03/2579.html

another one here

http://www.itworld.com/Comp/3380/nls_unixchown040923/index.html

The reasoning explained sounds logical. Apparantly (as one of the article also explains), the restriction helps a user fill another user’s quota by creating a huge file and chowning it to the other user. Even worse, if the other user doesnt have privs to access the dir hosting that huge file, he cant even delete that.

Looks like a safety precaution, turned into a bit of blockade for normal users…

inet daemons : the way they react to SMF

For a given service, in an SMF manifest, you can invoke any script using the “exec” thing. That works for normal programs.

You can also provide environment to the executable by adding sub-tags envvar..

However, For a network daemon based service, it wont work as nice as it does for other programs.

I came to understand that programs that run as streams need to be designed to work that way specifically, you cant just make ANY program run as a stream through an SMF service.

Using Solaris SMF : Initial Steps

Startup article about SMF usage..

O’Reilly Network — Using Solaris SMF: “In most Unix environments, the startup process consists of a handful of autonomous boot scripts। They act independently of one another; unaware of what scripts have already run or which ones will run after them. When they are invoked, there is no serious error checking and no recourse if the script fails.”

Another interesting tutorial from Sun… Solaris Operating System – SMF Manifest How To Guide