These errors have all been fixed. Changes were limited to qtp-build-sandbox.
You can get the latest release (v0.1.1) from qtp.shubes.net or svn.shubes.net.

Thank you for your patience (and testing!). ;)

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 ...
>>>     
>>
>> These are apparently from an older version. They are now in
>> /var/qmail/supervise/ instead of /var/service/. What toaster version
>> are you
>> upgrading from?
>>
>> 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. qmailtoaster is
> almost the last version and is working allright.
> 
> ---------------------------------------------------------------------
>     QmailToaster hosted by: VR Hosted <http://www.vr.org>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [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]

Reply via email to