OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 24-Mar-2004 17:31:39
Branch: HEAD Handle: 2004032416313800
Modified files:
openpkg-re upgrade.txt
Log:
log ulimit and openssh pitfall
Summary:
Revision Changes Path
1.42 +23 -1 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.41 -r1.42 upgrade.txt
--- openpkg-re/upgrade.txt 15 Mar 2004 22:18:03 -0000 1.41
+++ openpkg-re/upgrade.txt 24 Mar 2004 16:31:38 -0000 1.42
@@ -2,7 +2,7 @@
General Notes
=============
- o $Revision: 1.41 $. The most recent update of this file can be
+ o $Revision: 1.42 $. The most recent update of this file can be
downloaded from http://cvs.openpkg.org/openpkg-re/upgrade.txt
o This file upgrade.txt file talks about tweaks and quirks when
@@ -59,6 +59,28 @@
rpmdb: rebuilding RPM database (built-in RPM procedure)
rpmdb: performing read/write operation on RPM database
rpmdb: making sure RPM database files have consistent attributes
+
+ o RPM reports "Resource temporarily unavailable" during build
+
+ The OpenPKG build process restricts itself from consuming too much
+ resources by setting ulimit(1) through the %{l_build_ulim} macro.
+ This can lead to situations where the build of a package breaks at
+ arbitrary points. If you want to modify the limits redefine the
+ macro. For no limits set ~/.rpmmacros of the building user to %nil.
+
+ $ echo "%l_build_ulim %nil" >>$PREFIX/.rpmmacros
+
+ o openssh does not restart after upgrade
+
+ The OpenSSH daemon in OpenPKG 1.3 uses a different pid file than
+ the one in 2.0. The postinstall scriptlet running at the end of the
+ install process belongs to 2.0, does not find the previous pid file
+ and is unable to stop the old daemon. As a result it cannot start
+ the new daemon. Workaround is to either stop the old daemon before
+ the installation or to kill the old daemon manually. In both cases
+ the new daemon has to be started manually.
+
+ $ $PREFIX/etc/rc openssh start status
o the following options were renamed
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
