Don't fear the Centos.... I moved my QMT from Fedora 6 to Centos 5 last month. I used QMT-backup and QMT-restore. It have to say the move was almost as easy as copying the file from one machine to another. Just follow the readme and it's a breeze!!
The only problem I had was I had to reset the tcp.smtp file myself because it wasn't brought over in the backup. I think Jake fixed that now though. Phil -----Original message----- From: Francisco Paco Peralta [EMAIL PROTECTED] Date: Mon, 28 Apr 2008 12:34:58 -0400 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with Clamd update > Hi Eric, > > Does this mean it is time to move to Centos? I have been holding out until > the next version of the qmail (the rpm version).... > > [EMAIL PROTECTED] etc]# qtp-whatami > qtp-whatami v0.3 > DISTRO=Fedora Core > OSVER=4 > QTARCH=i686 > BUILD_DIST=fdr40 > BUILD_DIR=/usr/src/redhat > This machine's OS is supported, but this version/arch has not been tested. > [EMAIL PROTECTED] etc]# yum check-update > Setting up repositories > dries 100% |=========================| 1.1 kB 00:01 > freshrpms 100% |=========================| 951 B 00:00 > qmailtoaster-plus 100% |=========================| 951 B 00:00 > extras 100% |=========================| 1.1 kB 00:00 > updates-released 100% |=========================| 951 B 00:00 > base 100% |=========================| 1.1 kB 00:00 > Reading repository metadata in from local files > > > Francisco "Paco" Peralta > > ----- Original Message ---- > From: Eric Shubert <[EMAIL PROTECTED]> > To: qmailtoaster-list@qmailtoaster.com > Sent: Monday, April 28, 2008 12:06:01 PM > Subject: Re: [qmailtoaster] Problems with Clamd update > > Paco, > > Looks like your compiler needs to be updated before you'll be able to update > clamav. > > What distro/ver are you running? > > # qtp-whatami > # yum check-update > > Francisco Paco Peralta wrote: > > Hi Eric, > > > > Nice to hear from you again. Here is what I have: > > > > [EMAIL PROTECTED] ~]# rpm -qa | grep toaster > > ezmlm-toaster-0.53.324-1.3.3 > > qmailmrtg-toaster-4.2-1.3.3 > > maildrop-toaster-2.0.3-1.3.5 > > libsrs2-toaster-1.0.18-1.3.3 > > send-emails-toaster-0.5-1.3.4 > > qmailadmin-toaster-1.2.11-1.3.4 > > daemontools-toaster-0.76-1.3.3 > > courier-authlib-toaster-0.59.2-1.3.6 > > isoqlog-toaster-2.1-1.3.4 > > simscan-toaster-1.3.1-1.3.6 > > ucspi-tcp-toaster-0.88-1.3.5 > > courier-imap-toaster-4.1.2-1.3.7 > > qmail-pop3d-toaster-1.03-1.3.15 > > vpopmail-toaster-5.4.17-1.3.4 > > ripmime-toaster-1.4.0.6-1.3.3 > > maildrop-toaster-devel-2.0.3-1.3.5 > > squirrelmail-toaster-1.4.11-1.3.8 > > vqadmin-toaster-2.3.4-1.3.3 > > ezmlm-cgi-toaster-0.53.324-1.3.3 > > qmailtoaster-plus.repo-0.1-1 > > qmailtoaster-plus-0.3.0-1.4.4 > > spamassassin-toaster-3.2.3-1.3.12 > > autorespond-toaster-2.0.4-1.3.3 > > libdomainkeys-toaster-0.68-1.3.3 > > control-panel-toaster-0.5-1.3.4 > > qmail-toaster-1.03-1.3.15 > > [EMAIL PROTECTED] ~]# service qmail stat > > authlib: up (pid 20185) 68691 seconds > > clamd: down 68666 seconds, normally up > > imap4: up (pid 20144) 68692 seconds > > imap4-ssl: up (pid 20151) 68692 seconds > > pop3: up (pid 20194) 68691 seconds > > pop3-ssl: up (pid 20208) 68691 seconds > > send: up (pid 20165) 68691 seconds > > smtp: up (pid 20178) 68691 seconds > > spamd: up (pid 20136) 68692 seconds > > submission: up (pid 20171) 68691 seconds > > authlib/log: up (pid 20190) 68691 seconds > > clamd/log: down 68666 seconds, normally up > > imap4/log: up (pid 20149) 68691 seconds > > imap4-ssl/log: up (pid 20157) 68692 seconds > > pop3/log: up (pid 20197) 68691 seconds > > pop3-ssl/log: up (pid 20210) 68691 seconds > > send/log: up (pid 20167) 68691 seconds > > smtp/log: up (pid 20183) 68691 seconds > > spamd/log: up (pid 20138) 68692 seconds > > submission/log: up (pid 20175) 68691 seconds > > [EMAIL PROTECTED] ~]# tail -100 /usr/src/qtp-upgrade/log/build-recent.log > > ++ basename ./config/config.sub > > + '[' -f /usr/lib/rpm/redhat/config.sub ']' > > + /bin/rm -f ./config/config.sub > > ++ basename ./config/config.sub > > + /bin/cp -fv /usr/lib/rpm/redhat/config.sub ./config/config.sub > > `/usr/lib/rpm/redhat/config.sub' -> `./config/config.sub' > > + for i in '$(find . -name config.guess -o -name config.sub)' > > ++ basename ./config/config.guess > > + '[' -f /usr/lib/rpm/redhat/config.guess ']' > > + /bin/rm -f ./config/config.guess > > ++ basename ./config/config.guess > > + /bin/cp -fv /usr/lib/rpm/redhat/config.guess ./config/config.guess > > `/usr/lib/rpm/redhat/config.guess' -> `./config/config.guess' > > + ./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu > > --target=i686-redhat-linux-gnu --program-prefix= --prefix=/usr > > --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin > > --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include > > --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var > > --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info > > checking build system type... i686-redhat-linux-gnu > > checking host system type... i686-redhat-linux-gnu > > checking target system type... i686-redhat-linux-gnu > > creating target.h - canonical system defines > > checking for a BSD-compatible install... /usr/bin/install -c > > checking whether build environment is sane... yes > > checking for a thread-safe mkdir -p... /bin/mkdir -p > > checking for gawk... gawk > > checking whether make sets $(MAKE)... yes > > checking for gawk... (cached) gawk > > checking for a BSD-compatible install... /usr/bin/install -c > > checking whether ln -s works... yes > > checking whether make sets $(MAKE)... (cached) yes > > checking for style of include used by make... GNU > > checking for i686-redhat-linux-gnu-gcc... no > > checking for gcc... gcc > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > checking for suffix of object files... o > > checking whether we are using the GNU C compiler... yes > > checking whether gcc accepts -g... yes > > checking for gcc option to accept ISO C89... none needed > > checking dependency style of gcc... gcc3 > > checking for a sed that does not truncate output... /bin/sed > > checking for grep that handles long lines and -e... /bin/grep > > checking for egrep... /bin/grep -E > > checking for ld used by gcc... /usr/bin/ld > > checking if the linker (/usr/bin/ld) is GNU ld... yes > > checking for /usr/bin/ld option to reload object files... -r > > checking for BSD-compatible nm... /usr/bin/nm -B > > checking how to recognize dependent libraries... pass_all > > checking how to run the C preprocessor... gcc -E > > checking for ANSI C header files... yes > > checking for sys/types.h... yes > > checking for sys/stat.h... yes > > checking for stdlib.h... yes > > checking for string.h... yes > > checking for memory.h... yes > > checking for strings.h... yes > > checking for inttypes.h... yes > > checking for stdint.h... yes > > checking for unistd.h... yes > > checking dlfcn.h usability... yes > > checking dlfcn.h presence... yes > > checking for dlfcn.h... yes > > checking the maximum length of command line arguments... 98304 > > checking command to parse /usr/bin/nm -B output from gcc object... ok > > checking for objdir... .libs > > checking for i686-redhat-linux-gnu-ar... no > > checking for ar... ar > > checking for i686-redhat-linux-gnu-ranlib... no > > checking for ranlib... ranlib > > checking for i686-redhat-linux-gnu-strip... no > > checking for strip... strip > > checking if gcc supports -fno-rtti -fno-exceptions... no > > checking for gcc option to produce PIC... -fPIC > > checking if gcc PIC flag -fPIC works... yes > > checking if gcc static flag -static works... yes > > checking if gcc supports -c -o file.o... yes > > checking whether the gcc linker (/usr/bin/ld) supports shared > > libraries... yes > > checking whether -lc should be explicitly linked in... no > > checking dynamic linker characteristics... GNU/Linux ld.so > > checking how to hardcode library paths into programs... immediate > > checking whether stripping libraries is possible... yes > > checking if libtool supports shared libraries... yes > > checking whether to build shared libraries... yes > > checking whether to build static libraries... yes > > configure: creating libtool > > checking for ANSI C header files... (cached) yes > > checking for C/C++ restrict keyword... __restrict > > checking for an ANSI C-conforming const... yes > > checking for inline... inline > > checking whether FPU byte ordering is bigendian... no > > checking whether byte ordering is bigendian... no > > checking for a supported version of gcc... ok (4.0.2) > > checking for gcc bug PR27603... ok, bug not present > > checking for gcc bug PR26763-2... ok, bug not present > > checking for valid code generation of CLI_ISCONTAINED... ok, bug not present > > checking for gcc bug PR28045... configure: error: your compiler has gcc > > PR28045 bug, use a different compiler, see > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28045 > > error: Bad exit status from /var/tmp/rpm-tmp.84340 (%build) > > > > > > RPM build errors: > > Bad exit status from /var/tmp/rpm-tmp.84340 (%build) > > [EMAIL PROTECTED] ~]# > > > > > > > > Francisco "Paco" Peralta > > > > > > ----- Original Message ---- > > From: Eric Shubert <[EMAIL PROTECTED]> > > To: qmailtoaster-list@qmailtoaster.com > > Sent: Saturday, April 26, 2008 9:14:04 PM > > Subject: Re: [qmailtoaster] Problems with Clamd update > > > > Francisco Paco Peralta wrote: > >> I have a couple of issues and I need some help if anyone could be so kind. > >> > >> > >> My first issue is that I am getting an email every 5 minutes that has > >> the following as text in the subject and I would like to stop it: > >> > >> Cron <[EMAIL PROTECTED]> env LANG=C /usr/bin/mrtg > >> /usr/share/toaster/mrtg/qmailmrtg.cfg 2>&1 > /dev/null > >> > >> My second issue is that I tried to update clamav and spamassassin > >> using qtp-newmodel and I believe I had trouble during the rpmbuild > >> portion for clamav. When I restarted qmail I started to get continuous > >> messages on the screen about a file missing for clamav, in a panic I did > >> the following: > >> > >> # vi /var/qmail/control/simcontrol > >> changed spam and clam into no > >> # service qmail cdb > >> > >> # svc -d /var/qmail/supervise/clamd /var/qmail/supervise/clamd/log > >> > >> > >> Just want to update my clamd but I have not been successful....help > >> > >> > >> Francisco "Paco" Peralta > >> > > > > Hey Paco, > > > > Please post the contents of /usr/src/qtp-upgrade/log/build-recent.log and > > we'll see if we can get you going again. > > > > Also, the results of: > > # rpm -qa | grep toaster > > # service qmail stat > > > > -- > > -Eric 'shubes' > > > > --------------------------------------------------------------------- > > QmailToaster hosted by: VR Hosted <http://www.vr.org> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > -Eric 'shubes' > > --------------------------------------------------------------------- > QmailToaster hosted by: VR Hosted <http://www.vr.org> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
