diff options
| author |   Duncan Roe | 2017-06-22 12:26:08 +0200 |
|---|---|---|
| committer |   Willy Sudiarto Raharjo | 2017-06-24 03:32:21 +0200 |
| commit | 888ec031aca7e4f81a72497f9ebc0259e07621cb (patch) | |
| tree | 0fcfcba8c18643f6a6111d70b341326312acc27e /network/netqmail/tests/README | |
| parent | a8e78c52c72b342c5436f5ff39148a3f2e68f7ee (diff) | |
| download | slackbuilds-888ec031aca7e4f81a72497f9ebc0259e07621cb.tar.gz | |
network/netqmail: Added (the qmail MTA).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'network/netqmail/tests/README')
| -rw-r--r-- | network/netqmail/tests/README | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/network/netqmail/tests/README b/network/netqmail/tests/README new file mode 100644 index 0000000000..02b5e5286f --- /dev/null +++ b/network/netqmail/tests/README @@ -0,0 +1,31 @@ +makechroot + +Make a chroot-able tree in which to run installpkg or explodepkg netqmail (i.e. +from an interactive instance of chroot). +Can also test installpkg --root to this tree. + +Whatever you do, you can step through the script commands in a root window. +After explodepkg, you can step through the install scripts. + +See ../README.SBo for mkchroot caveats. Approximate disk usage: 1.5MB local +$CHROOT, 131MB mounted $CHROOT. + +Set CHROOT to dir to buid (will be removed & re-created) (default is /tmp/t5). +Set PKGDIR to directory containing SBo packages (default is /usr/packages). +Set STRIP_INITTAB_SV=no to leave the SV line added by daemontools (dflt yes). +Set INSTALL_DAEMONTOOLS=yes to install daemontools (default is no). +Set STRIP_QMAIL_USERS_GROUPS=no to retain qmail users and groups (dflt yes). +Set VERBOSE_ADDCHROOT=false to suppress install progress reporting (dflt true). +Set MKCHROOT_IGNORE_LN_ERRORS=yes to suppress error messages from mounted chroot + +If you specified INSTALL_DAEMONTOOLS=yes, you can try running inst_check from an +interactive chroot instance (qmail installation checker). +inst_check will tell you to mount /proc - be sure to umount it afterwards. +*if* the main system is running svscanboot, *and* the main system is not running +an MTA, on re-running inst_check you should see + + Congratulations, your LWQ installation looks good! + +Otherwise you should see a self-explanatory error message. If the main system is +not runninmg svscanboot, you can start it in the chroot environment. +Remember to umount /proc before exitting chroot. |