Martin Michlmayr wrote: > INIT: Entering runlevel: 2 > Starting system log daemon.... > Starting kernel log daemon.... > Starting OpenBSD Secure Shell server: sshd. > Starting periodic command scheduler: crond. > > Below are the last few messages in syslog. I ran out of time before I > was able to fully investigate this problem, so I don't know if it is a > symptom of using lowmem level 1 for the installation. > > Oct 22 12:08:44 LKG7102D7 /usr/sbin/cron[1790]: (CRON) INFO (pidfile fd = 3) > Oct 22 12:08:44 LKG7102D7 /usr/sbin/cron[1791]: (CRON) STARTUP (fork ok) > Oct 22 12:08:44 LKG7102D7 /usr/sbin/cron[1791]: (CRON) INFO (Running > @reboot jobs) > Oct 22 12:08:51 LKG7102D7 kernel: eth1: no IPv6 routers present > Oct 22 12:17:01 LKG7102D7 /USR/SBIN/CRON[1891]: (root) CMD ( cd / && > run-parts --report /etc/cron.hourly)
Does /etc/inittab have a correctly configured getty? Cron is probably just the last service started. > This test did show that the installer doesn't run out of memory in > lowmem level 1 using guided partitioning Excellent! > but I should try manual > partitioning, and also should look at the available memory at various > stages of the installation to see how close the installer is to > running out of memory, assuming there is enough memory left to run > shell :-) Yep. > The difference is probably due to swapping when apt is running because > there is less memory (RAM) available. I agree. -- see shy jo
signature.asc
Description: Digital signature
