Eric "Shubes" wrote:
Lucian Cristian wrote:
Eric "Shubes" wrote:
Lucian Cristian wrote:
I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
free disk space/14 used) and it have the following output (sandbox is
copyed, not linked)
<<
...
Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/spool/postfix/public/pickup
prw--w--w- 1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
Continuing ...
Unexpected named pipe: /var/spool/postfix/public/qmgr
prw--w--w- 1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
Continuing ...
This doesn't look kosher for a toaster:
1) Is postfix installed? I thought it couldn't coexist with qmail. Why
does
/var/spool/postfix exist?
2) User:group 89:89 not defined? That should normally be vpopmail, but I
suppose it could be any other number.
Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
prw------- 1 root root 0 Dec 4 2005
/var/service/qmail-pop3d/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-pop3d/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-pop3d/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-pop3d/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/control
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-send/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/ok
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-send/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/control
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-send/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-send/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
prw------- 1 root root 0 Dec 4 2005
/var/service/qmail-smtpd/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-smtpd/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-smtpd/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
prw------- 1 root root 0 Dec 3 2005
/var/service/qmail-smtpd/log/supervise/ok
Continuing ...
This doesn't hurt anything, as they're not used. I'll update the
script to
create them though (and thus get rid of the messages).
Unexpected file type for /var/run/pure-ftpd/client-00011531
ls: /var/run/pure-ftpd/client-00011531: No such file or directory
Continuing ...
This was apparently (I'm guessing) a transient file from an ftp
session that
disappeared during the run. I'll fix the script to handle the /var/run
directory more appropriately.
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw---- 1 root root 0 Oct 18 2005 /var/gdm/.gdmfifo
Continuing ...
I'll fix this one too.
cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
or resou
rce busy
cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument
Hmmm, a chroot within a chroot. This is a problem all right. I'm
surprised
to realize that I haven't tested this since I added named-chroot. I'm
getting a boatload of errors at this point too. I'm going to fix this
right
now. I'll post to the list when it's fixed and tested, should be later
today.
( here I pressed CTRL+C )
bash-3.00#
Thanks, Lucian.
Sometime ago I tested a postfix install and a qmail from original site
install, maybe that's why I have those files there.
I'd lose them.
qmailtoaster is almost the last version and is working allright.
"Almost is good enough for quoits and hand grenades". :)
I ask because I don't want to add checks in the script for /var/service/
pipes if it's not necessary. Do you have /var/qmail/supervise/ files too? If
so, you can lose /var/service/ too. I'd like to know where it came from
though. If it's an older toaster (as I suspect), I'll leave them in the
script. I wonder if they're simply left over from a previous version. What
was the first toaster version on that box? The directories are dated 12/3/05.
P.S. Fixed script final test is running now...
this are my qmailtoaster files:
autorespond-toaster-2.0.4-1.3.1.i386.rpm
clamav-toaster-0.88.2-1.3.1.i386.rpm
courier-authlib-toaster-0.58-1.3.1.i386.rpm
courier-imap-toaster-4.1.1-1.3.2.i386.rpm
daemontools-toaster-0.76-1.3.1.i386.rpm
ezmlm-cgi-toaster-0.53.324-1.3.1.i386.rpm
ezmlm-toaster-0.53.324-1.3.1.i386.rpm
isoqlog-toaster-2.1-1.3.1.i386.rpm
libdomainkeys-0.68-1.0.1.i386.rpm
libdomainkeys-toaster-0.68-1.3.1.i386.rpm
maildrop-toaster-2.0.2-1.3.1.i386.rpm
maildrop-toaster-devel-2.0.2-1.3.1.i386.rpm
qmailadmin-toaster-1.2.9-1.3.1.i386.rpm
qmailmrtg-toaster-4.2-1.3.1.i386.rpm
qmail-pop3d-toaster-1.03-1.3.3.i386.rpm
qmail-toaster-1.03-1.3.3.i386.rpm
ripmime-toaster-1.4.0.6-1.3.1.i386.rpm
simscan-toaster-1.2-1.3.1.i386.rpm
spamassassin-toaster-3.1.3-1.3.1.i386.rpm
ucspi-tcp-toaster-0.88-1.3.1.i386.rpm
vpopmail-toaster-5.4.13-1.3.1.i386.rpm
vqadmin-toaster-2.3.4-1.3.1.i386.rpm
zlib-1.2.3-1.0.3.i386.rpm
zlib-devel-1.2.3-1.0.3.i386.rpm
I've removed the /var/service directory.
About the version, I wanted to update using the qtp-newmodel and this
machine is last priority, it only has one email acount :)
Anyway I am very glad that I found this site, I'm very pleased to use
qmailtoaster.
Thanks all of you !
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]