>
> Hello,
>
> Typing msec produces the following :
> /usr/share/msec/.py not found or not executable. Aborting
>
/usr/sbin/msec:
if [ -n "$last" ]; then
case $last in
[0-5]) ;;
*) [ -x /usr/share/msec/$last.py ] &&
MSEC=/usr/share/msec/$last.py;;
esac
else
# no args so try to guess if a custom msec is needed
. /etc/sysconfig/msec
case "$SECURE_LEVEL" in
[0-5]) ;;
*) MSEC=/usr/share/msec/$SECURE_LEVEL.py;;
esac
fi
Fredl, please:
- ship msec with default /etc/sysconfig/msec
- make it compatible with current SECURITY in /etc/sysconfig/system i.e.
= initialize SECURE_LEVEL from SECURITY
= fall back in msec to SECURITY if no SECURE_LEVEL is found
- please give more sane error message if security level cannot be
determined; instead of
echo "/usr/share/msec/$last.py not found or not executable. Aborting"
something like
echo "Cannot determine security level. Please SECURE_LEVEL=n in
/etc/sysconfig/msec. Aborting"
Finally is mcc aware of this change?
Owen, just do
cat > /etc/sysconfig/msec
SECURE_LEVEL=...
^D
-andrej
