Slack 11.0 postfix from SlackBuilds - problem
in [Slackware]
|
Prev: slack 13.0 DVD Burning
Next: Menu editing in KDE 4.2
From: +Alan Hicks+ on 10 Dec 2009 18:34 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2009-12-08, Rich Grise <richgrise(a)example.net> wrote: > When my system got compromised, I asked how to fix it, and everybody > told me bare-metal reinstall. I emailed Alan Hicks and asked if I should > know anything, and he said what to back up, then use his SlackBuild > scripts, and he said, "The SlackBuild scripts at the above web site > should make this almost trivial. " > > Well, somehow in the last two hours, I've managed to create the > package postfix-2.4.1-i486-1_SBo.tgz, but when I run installpkg on it, > I get: > > "Installing package postfix-2.4.1-i486-1_SBo... <snip> > Executing install script for postfix-2.4.1-i486-1_SBo... > chown: missing operand after `postfix' > Try `chown --help' for more information." > > I've chowned my whole postfix dir tree to root:root; what am I missing > _NOW_? The fact that your whole postfix dir tree should not be root:root after installing. Several files and directories installed by postfix need special user and/or group permissions for security purposes. postfix is fairly unique in that the Makefile does not set permissions on the different files and directories before the package is created. Rather there is a special argument to the postfix binary that handles this. The doinst.sh script attempts to resolve this for you. Apparently that has not worked in this case. Did you create the postfix user and postdrop group as stated in the build script? Did you by chance already have an existing /etc/postfix directory when you installed this package? Either of those could possibly result in this error if they were not done properly. You can attempt to repair this problem after installation by running the following command as root: # postfix set-permissions This should resolve the permissions problems, assuming of course that the user and group are properly setup, and that the configuration files in /etc/postfix are correct. - -- It is better to hear the rebuke of the wise, Than for a man to hear the song of fools. Ecclesiastes 7:5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkshhYQACgkQNj1TaGS9H5JyMwCaA/ptaTaEXkW7/e9U+WDZRa6k 6lwAn1jIlvwUzLmVfVZwCdaBNaabxjL2 =JD/K -----END PGP SIGNATURE-----
From: Rich Grise on 11 Dec 2009 14:55 On Thu, 10 Dec 2009 23:34:29 +0000, +Alan Hicks+ wrote: > On 2009-12-08, Rich Grise <richgrise(a)example.net> wrote: >> When my system got compromised, I asked how to fix it, and everybody >> told me bare-metal reinstall. I emailed Alan Hicks and asked if I should >> know anything, and he said what to back up, then use his SlackBuild >> scripts, and he said, "The SlackBuild scripts at the above web site >> should make this almost trivial. " >> >> Well, somehow in the last two hours, I've managed to create the package >> postfix-2.4.1-i486-1_SBo.tgz, but when I run installpkg on it, I get: >> >> "Installing package postfix-2.4.1-i486-1_SBo... > <snip> >> Executing install script for postfix-2.4.1-i486-1_SBo... chown: missing >> operand after `postfix' Try `chown --help' for more information." >> >> I've chowned my whole postfix dir tree to root:root; what am I missing >> _NOW_? > > The fact that your whole postfix dir tree should not be root:root after > installing. Several files and directories installed by postfix need > special user and/or group permissions for security purposes. postfix is > fairly unique in that the Makefile does not set permissions on the > different files and directories before the package is created. Rather > there is a special argument to the postfix binary that handles this. The > doinst.sh script attempts to resolve this for you. Apparently that has not > worked in this case. > > Did you create the postfix user and postdrop group as stated in the build > script? Did you by chance already have an existing /etc/postfix directory > when you installed this package? Either of those could possibly result in > this error if they were not done properly. > > You can attempt to repair this problem after installation by running the > following command as root: > > # postfix set-permissions > > This should resolve the permissions problems, assuming of course that the > user and group are properly setup, and that the configuration files in > /etc/postfix are correct. > Thanks! Got it! Whew! ;-) Rich
From: Rich Grise on 11 Dec 2009 14:56
On Thu, 10 Dec 2009 23:34:29 +0000, +Alan Hicks+ wrote: > On 2009-12-08, Rich Grise <richgrise(a)example.net> wrote: >> When my system got compromised, I asked how to fix it, and everybody >> told me bare-metal reinstall. I emailed Alan Hicks and asked if I should >> know anything, and he said what to back up, then use his SlackBuild >> scripts, and he said, "The SlackBuild scripts at the above web site >> should make this almost trivial. " >> >> Well, somehow in the last two hours, I've managed to create the package >> postfix-2.4.1-i486-1_SBo.tgz, but when I run installpkg on it, I get: >> >> "Installing package postfix-2.4.1-i486-1_SBo... > <snip> >> Executing install script for postfix-2.4.1-i486-1_SBo... chown: missing >> operand after `postfix' Try `chown --help' for more information." >> >> I've chowned my whole postfix dir tree to root:root; what am I missing >> _NOW_? > > The fact that your whole postfix dir tree should not be root:root after > installing. Several files and directories installed by postfix need > special user and/or group permissions for security purposes. postfix is > fairly unique in that the Makefile does not set permissions on the > different files and directories before the package is created. Rather > there is a special argument to the postfix binary that handles this. The > doinst.sh script attempts to resolve this for you. Apparently that has not > worked in this case. > > Did you create the postfix user and postdrop group as stated in the build > script? Did you by chance already have an existing /etc/postfix directory > when you installed this package? Either of those could possibly result in > this error if they were not done properly. > > You can attempt to repair this problem after installation by running the > following command as root: > > # postfix set-permissions > > This should resolve the permissions problems, assuming of course that the > user and group are properly setup, and that the configuration files in > /etc/postfix are correct. > Thanks! Roger Wilco! Cheers! Rich |