On Fri, 21 Mar 2014, David Spencer wrote:
Strategy A is to observe more closely what the system is doing. Start the install, wait ten mins, and do 'vmstat 5 20' and 'iostat 5 20' and 'ps -efl' to see what's happening. Look for the tree of pids that starts with installpkg. This might reveal something like an i/o redirection that has gone wrong so that it's waiting forever for input (you might also want to try typing ctrl/d on the controlling terminal in case that's what's up).
David, Will do. It's still early here so it will be an hour or so before I get to this.
Strategy B is to think it through from the other end. Does the installpkg command print 'Executing install script for texlive-20130530-i486-2_SBo.tgz' before it seems to stop?
Yes, it does. There's a newline and there it sits.
I'm not sure what these commands do, but it might be interesting to remove '1>/dev/null 2>/dev/null' from them to see what shows up when the package is installed. (Maybe you could shortcircuit the need to rebuild the whole package by using explodepkg, editing install/doinst.sh, and making a new package with makepkg). Anybody else have some tips?
Let me try A and report results. Thanks, Rich _______________________________________________ SlackBuilds-users mailing list [email protected] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
