Solaris buildpkg.sh: postinstall script added

[Ben Lindstrom]

Hmm.. Not the package management's job to handle restarting of sevices.
+ if [ -f $PIDDIR/sshd.pid ]
+ then
+         pid=\`cat $PIDDIR/sshd.pid\`
+         if ps -p \$pid | grep sshd >/dev/null
+         then
+                 echo "Stopping sshd (pid \$pid)."
+                 kill \$pid
+         fi
+ fi


I don't like the idea.  I have personally never liked it.  I'd rather
have the post install script inform the admin that they must restart sshd
for the new version to take affect.

Reason being is there are times you install upgrade packages for
general testing, and you don't want them to kill your known good
sshd.  Even on test platforms.. =)  It makes people very growly when
they have to get up from their desks and restat sshd from the sun
console. =)

- Ben

On Sun, 3 Mar 2002, Darren Tucker wrote:

> Hello.
> 	I've added a postinstall script and a few mods to the Solaris
> buildpkg.sh to:
>
> * Save previous configs and create them from defaults if necessary
> * (re)start sshd
>
> This has been tested on Solaris 2.6 only.
>
> The patch can be had from either of:
> http://www.zip.com.au/~dtucker/openssh-3.0.2p1-buildpkg.patch
> http://home.usf.advantra.com.au/~dtucker/openssh-3.0.2p1-buildpkg.patch
>
> 		-Daz.
> _______________________________________________
> openssh-unix-dev at mindrot.org mailing list
> http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
>