Donations

Donate to support our development efforts.


Languages
Change language | Change language | Change language | Change language | Change language | Change language | Change language | Change language | Change language | Change language
Share

Share Frugalware with your friends.








Frugalware
on Google+
Recent updates
devel-extra/mako
0.8.1-1-arm
devel/numpy
1.7.1-1-arm
devel-extra/scipy
0.12.0-1-i686
devel-extra/mako
0.8.1-1-i686
devel-extra/
 perl-compress-bzip2
2.16-1-i686
lib-extra/liburcu
0.7.7-1-i686
lib-extra/leveldb
1.12.0-1-i686
apps-extra/rdfind
1.3.4-1-i686
devel/numpy
1.7.1-1-i686
devel-extra/
 ruby-cabin
0.6.1-1-i686

RSS
Information
Go Frugalware, Go
Valid XHTML 1.0!
Valid CSS!
Valid RSS!
Server information
Uptime:
64 day(s) 9 h 40 m 20 s

There has been an update to current in regards to systemd. During testing, there was discovered to be some issues with reboots and shutdowns appearing to 'hang'.
Further inspection revealed that the behavior was caused by display-manager.service refusing to shutdown in a timely manner, by systemd's definition. The process
still works out in the end, provided you wait long enough for the effected service to be forced to terminate by timeout. This is a public announcement, in the
event you experience a 'hang' during reboot or shutdown, that you should try waiting it out. The default timeout per service is 90 seconds, so it may take awhile.
If you want more details as to what is going on during this 'hang', you should boot without the 'splash' and 'quiet' boot arguments. Thank you.

Posted by ryuo - Sun, 19 Feb 2012 12:01:34 -0600



© 2003-2011. The Frugalware Developer Team