On Thu, Oct 25, 2007, Ralf S. Engelschall wrote:

>   OpenPKG CVS Repository
>   http://cvs.openpkg.org/
>   ____________________________________________________________________________
> 
>   Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
>   Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
>   Module: openpkg-src                      Date:   25-Oct-2007 19:04:06
>   Branch: HEAD                             Handle: 2007102518040400
> 
>   Added files:
>     openpkg-src/op          op.conf op.spec
> 
>   Log:
>     new package: op 1.32 (Controlled Operator Privilege Escalation)
[...]
>   +    case "%{l_platform -t}" in
>   +        *-freebsd* )
>   +            l_su="/bin/su"
>   +            l_shutdown="/usr/bin/shutdown -h now"
>   +            l_reboot="/usr/bin/shutdown -r now"
>   +            ;;
>   +        *-linux* )
>   +            l_su="/bin/su"
>   +            l_shutdown="/bin/shutdown -h now"
>   +            l_reboot="/bin/shutdown -r now"
>   +            ;;
>   +        *-sunos* )
>   +            l_su="/usr/bin/su"
>   +            l_shutdown="/usr/bin/shutdown -i0 -g0 -y"
>   +            l_reboot="/usr/bin/shutdown -i6 -g0 -y"
>   +            ;;
>   +        * )
>   +            l_su="`%{l_shtool} path su`"
>   +            l_shutdown="`%{l_shtool} path shutdown` -h now"
>   +            l_reboot="`%{l_shtool} path shutdown` -r now"
>   +            ;;
>   +    esac
[...]

Ralf, I don't think it's a good idea to shutdown paths here, in
general they are not correct. At least on my FreeBSD boxes, it's
"/sbin/shutdown", and well, under Linux, which distribution flavor do
you like? On Debian, it is "/sbin/shutdown". I would suggest, just
to hardcode the shutdown parameters for each platform and let
"shtool path" do the rest on all platforms.

-cs
______________________________________________________________________
OpenPKG                                             http://openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to