Newsgroup: it.comp.os.win.software
Titolo: [MAndrake 7.1] Problemi con Inn + tin newsreader...[Richiesta di aiuto]

 Cosa potrebbe essere?
Ancora non lo so...:-((
Ecco come ho fatto, spero non me ne vogliate per la lunghezza....
sono entrato come normale utente
ho dato il comando
su
e sono "diventato" root...
inizialmente sono riuscito a far viaggiare innd...infatti
netstat -tuna
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 
0.0.0.0:119
             0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:6000
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:1024
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:25
              0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:515
             0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:31337
           0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:12345
           0.0.0.0:*               LISTEN
udp        0      0 
127.0.0.1:1119
          0.0.0.0:*
udp        0      0 
0.0.0.0:177
             0.0.0.0:*
udp        0      0 
0.0.0.0:517
             0.0.0.0:*
Poi l'ho interrotto...
/etc/rc.d/init.d/innd stop
Stopping INND service:  [60G[   [1;32mOK [0;39m  ]
Stopping INN actived service:  [60G[   [1;32mOK [0;39m  ]
                ^^^^^^^^^^^^^^^^^^^^
                A cosa servirà ?!?
e fin qui tutto ok, come conferma
netstat -tuna
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 
0.0.0.0:6000
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:1024
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:25
              0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:515
             0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:31337
           0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:12345
           0.0.0.0:*               LISTEN
udp        0      0 
0.0.0.0:177
             0.0.0.0:*
udp        0      0 
0.0.0.0:517
             0.0.0.0:*
Adesso provo a riattivarlo...
/etc/rc.d/init.d/innd start
Starting INND system:  [60G[   [1;32mOK [0;39m  ]
ottengo conferma positiva...ma...
netstat -tuna
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 
0.0.0.0:6000
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:1024
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:25
              0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:515
             0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:31337
           0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:12345
           0.0.0.0:*               LISTEN
udp        0      0 
127.0.0.1:1119
          0.0.0.0:*
udp        0      0 
0.0.0.0:177
             0.0.0.0:*
udp        0      0 
0.0.0.0:517
             0.0.0.0:*
è attivo solo innd active service...[???]
interrompo nuovamente
/etc/rc.d/init.d/innd stop
Stopping INN actived service:  [60G[   [1;32mOK [0;39m  ]
e adesso invece lancio l'altro script...
/etc/rc.d/rc.news start
Starting innd.
Tutto ok!! Come si può notare
netstat -tuna
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 
0.0.0.0:119
             0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:6000
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:1024
            0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:25
              0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:515
             0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:31337
           0.0.0.0:*               LISTEN
tcp        0      0 
0.0.0.0:12345
           0.0.0.0:*               LISTEN
udp        0      0 
127.0.0.1:1119
          0.0.0.0:*
udp        0      0 
0.0.0.0:177
             0.0.0.0:*
udp        0      0 
0.0.0.0:517
             0.0.0.0:*
Tutto è partito alla grande ma...
perchè solo con questo script? Vorrei proprio capirlo...
Vi ho allegato anche gli script...:
Questo è /etc/rc.d/rc.news
#!/bin/sh
##  $Revision: 1.22.2.1 $
##  News boot script.  Runs as "news" user.  Requires inndstart be
##  setuid root.  Run from rc.whatever as:
##     su news -c /path/to/rc.news >/dev/console
. /usr/lib/innshellvars
AZ=ABCDEFGHIJKLMNOPQRSTUVWXYZ
az=abcdefghijklmnopqrstuvwxyz
##  Pick ${INND} or ${INNDSTART}
WHAT=${INNDSTART}
##  Set to true or false
: ${DOINNWATCH:=true}
DOINNWATCH=`echo ${DOINNWATCH} | tr ${AZ} ${az}`
if [ -z "${DOINNWATCH}" \
     -o "${DOINNWATCH}" = "on" \
     -o "${DOINNWATCH}" = "true" \
     -o "${DOINNWATCH}" = "yes" ]; then
    DOINNWATCH=true
else
    DOINNWATCH=false
fi
: ${DOCNFSSTAT:=false}
DOCNFSSTAT=`echo ${DOCNFSSTAT} | tr ${AZ} ${az}`
if [ -z "${DOCNFSSTAT}" \
     -o "${DOCNFSSTAT}" = "on" \
     -o "${DOCNFSSTAT}" = "true" \
     -o "${DOCNFSSTAT}" = "yes" ]; then
    DOCNFSSTAT=true
else
    DOCNFSSTAT=false
fi
MAIL="${MAILCMD} -s 'Boot-time Usenet warning on `hostname`' ${NEWSMASTER}"
##  RFLAG is set below; set INNFLAGS in inn.conf(5)
RFLAG=""
##  Clean shutdown or already running?
if [ -f ${SERVERPID} ] ; then
    if kill -0 `cat ${SERVERPID}` 2>/dev/null; then
 echo 'INND is running'
 exit 0
    fi
    echo 'INND:  PID file exists -- unclean shutdown!'
    RFLAG="-r"
fi
if [ ! -f ${PATHDB}/.news.daily ] ; then
    case `find ${PATHBIN}/innd -mtime +1 -print 2>/dev/null` in
    "")
 ;;
    *)
 echo 'No .news.daily file; need to run news.daily?' | eval ${MAIL}
 ;;
    esac
else
    case `find ${PATHDB}/.news.daily -mtime +1 -print 2>/dev/null` in
    "")
 ;;
    *)
 echo 'Old .news.daily file; need to run news.daily?' | eval ${MAIL}
 ;;
    esac
fi
##  Active file recovery.
if [ ! -s ${ACTIVE} ] ; then
    if [ -s ${NEWACTIVE} ] ; then
 mv ${NEWACTIVE} ${ACTIVE}
    else
 if [ -s ${OLDACTIVE} ] ; then
     cp ${OLDACTIVE} ${ACTIVE}
 else
     echo 'INND:   No active file!'
     exit 1
 fi
    fi
    RFLAG="-r"
    # You might want to rebuild the DBZ database, too:
    #cd ${PATHDB} \
    #  && makehistory -r \
    #  && mv history.n.dir history.dir \
    #  && mv history.n.index history.index \
    #  && mv history.n.hash history.hash
fi
##  Remove temporary batchfiles and lock files.
( cd ${BATCH} && rm -f bch* )
( cd ${LOCKS} && rm -f LOCK* )
( cd ${TEMPSOCKDIR} && rm -f ${TEMPSOCK} )
rm -f ${NEWSCONTROL} ${NNTPCONNECT} ${SERVERPID}
##  Start the show.
echo 'Starting innd.'
eval ${WHAT} ${RFLAG} ${INNFLAGS}
# Gee, looks like lisp, doesn't it?
${DOINNWATCH} && {
    echo "Scheduled start of ${INNWATCH}."
    ( sleep 60 ; ${INNWATCH} ) &
}
${DOCNFSSTAT} && {
    echo "Scheduled start of cnfsstat."
    ( sleep 60 ; ${PATHBIN}/cnfsstat -s -l ) &
}
RMFILE=${MOST_LOGS}/expire.rm
for F in ${RMFILE} ${RMFILE}.*; do
    if [ -f $F -a -s $F ] ; then
 echo "Removing articles from pre-downtime expire run (${F})."
 (
     echo 'System shut down during expire.' \
  'Unlinking articles listed in'
     echo ${F}
 ) | eval ${MAIL}
 ${PATHBIN}/expirerm ${F}
    fi
done &
Mentre quest'altro è...
/etc/rc.d/init.d/innd
#! /bin/sh
#
# innd  InterNet News System
#
# chkconfig: 345 95 05
# description: inn is the most popular server for Usenet news. It allows \
#              you to setup local news servers. It can be difficult to \
#              set up properly though, so be sure to read /usr/doc/inn* \
#              before trying.
# processname: innd
# pidfile: /var/run/news/innd.pid
# Source function library.
. /etc/rc.d/init.d/functions
# Get config.
. /etc/sysconfig/network
# Check that networking is up.
if [ ${NETWORKING} = "no" ]
then
 exit 0
fi
[ -d /etc/news ] || exit 0
[ -d /usr/lib/news ] || exit 0
[ -d /var/spool/news ] || exit 0
# See how we were called.
case "$1" in
  start)
 echo -n "Starting INND system: "
 su news -c ". /etc/rc.d/init.d/functions ; daemon /etc/rc.d/rc.news"
 touch /var/lock/subsys/innd
 echo
 ;;
  stop)
 if [ -f /var/run/news/innd.pid ]
 then
  echo -n "Stopping INND service: "
  killproc innd
  rm -f /var/run/news/innd.pid
  echo
 fi
 if [ -f /var/run/news/innwatch.pid ]
 then
  echo -n "Stopping INNWatch service: "
  killproc innwatch -9
  rm -f /var/run/news/innwatch.pid
  echo
 fi
 if [ -f /var/run/news/innfeed.pid ]
 then
  echo -n "Stopping INNFeed service: "
  killproc innfeed -9
  rm -f /var/run/news/innfeed.pid
  echo
 fi
 if [ -f /var/run/news/actived.pid ]
 then
  echo -n "Stopping INN actived service: "
  killproc actived -9
  rm -f /var/run/news/actived.pid
  echo
 fi
 rm -f /var/lock/subsys/innd /var/lock/news/*
 ;;
  status)
 status innd
 ;;
  restart)
 echo -n "Restarting INN Service: "
 killproc innd -HUP
 echo
 ;;
  *)
 echo "Usage: $0 {start|stop|status|restart}"
 exit 1
 ;;
esac
exit 0
Dopo aver fatto tutto ciò che ho descritto [forse anche troppo] prima,
con un
tail -n 40 /var/log/news/*
ottengo...
==> /var/log/news/activedloads <==
==> /var/log/news/errlog <==
INND exiting because of signal
==> /var/log/news/expire.log <==
==> /var/log/news/expire.rm <==
==> /var/log/news/news <==
==> /var/log/news/news.crit <==
Apr 22 20:40:26 localhost innd: SERVER shutdown received signal 15
Apr 22 20:40:46 localhost inndstart: inndstart cant bind Permesso negato
Apr 22 20:41:50 localhost innd: SERVER cant exec in
/usr/lib/news/bin/crosspost Exec format error
Apr 22 20:41:50 localhost innd: SERVER cant exec in
/usr/lib/news/bin/controlchan Exec format error
==> /var/log/news/news.err <==
Apr 22 20:40:46 localhost inndstart: inndstart cant setgroups Operazione non
permessa
Apr 22 20:41:50 localhost innd: SERVER perl filter not defined
==> /var/log/news/news.notice <==
==> /var/log/news/nntpsend.log <==
==> /var/log/news/OLD <==
==> /var/log/news/unwanted.log <==
E questi sono i problemi + grossi.
[prima di iniziare avevo "pulito i log]
errlog non l'ho capito...forse intende che l'ho chiuso io con
/etc/rc.d/init.d/innd stop ?
però mi sembra strano che logga una cosa consentita...in errlog poi....ma
:-?
news.crit poi lo trovo incomprensibile.
Per paura che fosse causato da un installazione non avvenuta da root avevo
precedentemente levato e rimesso inn.
Consigli??
Per non parlare di news.err.....
sembra che inndstart non riesca proprio a partire... ma perchè?!? :-???
Poi, cosa significa che on ho definito il "perl filter" ?
Scusate ancora per la lunghezza spropositata, ma...appena risolvo il
problema abbandono win e mi lancio nel magnifico mondo linux :-))
Vorrei anche sapere come posso poi "dire" a innd di scaricarmi le news e di
inviarmele...
cosa devo lanciare/settare/leggere?
Un ultima domanda, dato che c sono...
per poi lanciare tin [newsreader]
tin -g 127.0.0.1 ????
grazie infinite, non saprò mai come ringraziarvi...vi farei un monumento
anche solo per essere arrivati a leggere fin qui...
Ciao a tutti e...scusate ancora!!
MaoX

Scusate...ho sbagliato a postare...
scusate davvero, non ho fatto apposta.
Grazie
    Maoz