(Aug 12 2005 10:02) Simone wrote: > Hi to all! > > Some time, when swup upgrade your package, that freeze it.
Looks like the cron job hangs, and I have not seen that on any live system I've used. Any change you have corruped memory or something? > Here crontab that run swup from Jul 27 > > [EMAIL PROTECTED] ~# ps fax | grep swup > 3312 ? S 0:00 \_ /bin/bash /etc/cron.daily/swup.cron > 3313 ? S 2:08 \_ /usr/bin/python > /usr/bin/swup --upgrade --quiet You can strace the processes, but they don't seem to do anything useful, so I guess you won't get anything useful output: strace -p 3312 or strace -p 3313 > Here error when I try to run "swup upgrade" manually > > [EMAIL PROTECTED] ~# swup --upgrade > Error: Lockfile /var/cache/swup/.lock exists. Exiting. > > Swup seems to be running with pid 3313. > The file may be manually removed, but only do this if you are sure that you > are not running any other swup processeses. > [EMAIL PROTECTED] ~# swup --upgrade > Error: Lockfile /var/cache/swup/.lock exists. Exiting. > > > > Is there solution for this problem? Killing the 3312 process or restarting fcron is probably what you need to do to fix it manually this time. > On every swup that upgrade you package, i need to kill manually that process Then you really need to have a look at your hardware. This is not typical behaviour, actually your're the first one to report this since swup was introduced back in 2001 (If memory serves me right). I'm guessing corrupt memory as swup uses a lot of it during large upgrades. kind regards c -- Christian H. Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
