Hello,
I've been having a problem with a weekly script I run to generate reports/statistics on my server.
This runs once a week and in the middle of the script, it issues a "go bg" command to restart the listserver and regenerate my listserv.log file.
What has been happening with the current setup is that it runs and generates the report but some of the statistics gained from the listserv.log.OLD file come up with zeros.
As it turns out, and after taking out the "respawn" option in my innittab file (solaris box), I've come to find that the "go bg" command hangs or something and listserv only partly restarts.  The new listserv.log file gets created and the old one is copied to listserv.log.OLD  Mail does get appear to be processed .. entries are logged into the listserv.log file (however, I don't think the mail is actually distributed) and the script never finishes.

If I leave the respawn option in the inittab file enabled, listserv gets restarted twice.
The listserv.log.OLD file is always left having only about 100-200K worth of data in it ... essentially the startup data.  The script then finishes.

Is there another way to start or restart the listserver to generate reports?
Is there something I may be missing?
I'll enclose the first part of my script just in case anyone might have any ideas or suggestions.

Thanks!,
Chris Barbot



# more run_stats
#!/bin/ksh
cd /export/home/listserv

# *******  Uncomment out the next two lines for production runs  ***********
cp -p listserv.log.OLD listservlog.$(date +%m%d%y)
compress listservlog.$(date +%m%d%y)
cp -p /export/home/listserv/weekly_stats weekly_stats.back

echo "              Weekly Statistics for $(hostname) on $(date +%A), $(date +%x) at $(date +%X)" > /export/home/listserv/weekly_stats

echo " " >> /export/home/listserv/weekly_stats
echo " " >> /export/home/listserv/weekly_stats


/usr/local/bin/lcmd show stats
sleep 2
tail -13  listserv.log >> /export/home/listserv/weekly_stats
echo " " >> /export/home/listserv/weekly_stats
/usr/local/bin/lcmd lists summary
sleep 2
tail -7  listserv.log >> /export/home/listserv/weekly_stats

#  *********  Uncomment out the following 2 lines for production run  ******
/export/home/listserv/go bg
sleep 5


# ********* These are SNMP statistics - They can be commented out if desired.
echo " " >> /export/home/listserv/weekly_stats
echo " " >> /export/home/listserv/weekly_stats
#/export/home/sscalsk/stats/sm.logger|head -13 >> weekly_stats
echo " " >> /export/home/listserv/weekly_stats
#/export/home/sscalsk/stats/smtpstats |head -5 >> weekly_stats

mailstats >> weekly_stats
cp -p /etc/ma/export/home/listserv/il/statistics /etc/mail/stats.bak
cp /dev/null /etc/mail/statistics


-----Original Message-----
From: Bill Earle [mailto:[log in to unmask]]
Sent: Tuesday, May 20, 2003 11:23 AM
To: [log in to unmask]
Subject: Listserv Test / DR offering? (fwd)
Importance: Low


Hello folks,

I have spoken with L-SOFT sales and they say I can use my current license
key in a test / DR server.  What I would like is some pointers /
recommendation on what others are doing for a disaster recovery Listserv
server.

We are listserv.buffalo.edu
 - Listserv HPO
 - Sun Fire 280R w/SCSI attached storage
 - Solaris
 - qmail mail transport

We would like to create a duplicate, (probably a new model server V240),
Listserv environment that would function as both a test env. and a DR env.
at our remote DR location..

Is there a way to have 2 Listserv servers automagically kept in sync. with
each other?

What methods are others using to create a test environment, a DR env?

Any information would be greatly appreciated.

Thanks in advance,
Bill

   William B. Earle     Computing & Information Technology
                        University at Buffalo
Voice: 716.645.6580     301 Computing Center
Fax:   716.645.5972     Buffalo, NY 14260