Solaris buildpkg.sh: postinstall script added

[Daniel Bergman]

I agree with Ben.
On a few occasions I've logged on to a server using an old SSH version, 
installed the new SSH package, killed the old SSH parent process and 
launched the new SSH for testing. If I'm satisfied with the new SSH version 
I would simply make it permanent and exit the forked-off old SSH process 
that I'm currently using, thus removing the old SSH version from the 
running system.

I think pre/post package scripts shouldn't mess with running processes.

Regards,
Daniel

> Ben Lindstrom wrote:
> [restarting daemons from postinstall scripts]
>> 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. =)
>
> As I said in a private (because I forgot to cc the list) message if you
> upgrade sshd and don't test it before logging out then you deserve what
> you get :-)
>
> Ben pointed out that it's a personal preference thing, and he's right.
> While it's really easy to restart it yourself if that's what you want
> it's too late if you didn't want to.
>
> So, how about:
>
># Check for running sshd and start if not running
> if [ -f $piddir/sshd.pid ]
> then
>         pid=\`cat $piddir/sshd.pid\`
>         if ps -p \$pid | grep sshd >/dev/null
>         then
>                 echo "sshd already running (pid \$pid)."
>         else
>                 echo "Starting sshd."
>                 $sbindir/sshd
>         fi
> fi
>
> 		-Daz.
> _______________________________________________
> openssh-unix-dev at mindrot.org mailing list
> http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
>
>



--
Daniel Bergman
Phone: 08 - 55066265
Mobile: 070 - 289 30 39
Fax: 08 - 59827056
Email: d-b at home.se