[Splashy-devel] Bug#485307: Bug#485307: splashy starts too late during startup/shutdown

[Kel Modderman]

On Tuesday 23 September 2008 18:43:44 Ritesh Raj Sarraf wrote:
> On Tuesday 23 Sep 2008 1:41:45 am Kel Modderman wrote:
> >
> > In addition to removing $all from Required-Stop, try adding:
> > X-Start-Before: mountdevsubfs udev
> >
> 
> Thanks. This solves the problem. With the above directive in place, we get 
> splashy listed just after mountkernfs and before any other scripts.
> 
> >
> > What is wrong if those scripts execute in parallel ?
> >
> 
> The problem I see here is this.
> rrs at learner:~$ ls /etc/rc6.d/
> K01anacron@       K01kvm@                         K01powersaved@    
> K02cryptdisks-early@  K10ifupdown@
> K01auditd@        K01laptop-mode@                 K01preload@       
> K02dhcdbd@            K11mountoverflowtmp@
> K01avahi-daemon@  K01libvirt-bin@                 K01pulseaudio@    
> K02hal@               K12umountfs@
> K01bluetooth@     K01network-manager@             K01resolvconf@    
> K03acpid@             K13lvm2@
> K01cryptdisks@    K01network-manager-dispatcher@  K01rsync@         
> K04dnsmasq@           K14umountroot@
> K01dictd@         K01nvidia-glx@                  K01samba@         
> K05rsyslog@           K15reboot@
> K01dirmngr@       K01nvidia-kernel@               K01spamassassin@  
> K06sendsigs@          README
> K01fuse@          K01openbsd-inetd@               K01splashy@       
> K07umountnfs.sh@
> K01kdm@           K01openvpn@                     K01urandom@       
> K09hwclock.sh@
> K01kerneloops@    K01policycoreutils@             K01wpa-ifupdown@  
> K09networking@
> 
> Majority of the services are K01. This leads to splashy still starting too 
> late.

Currently, there is no solution in insserv to insert a script at lowest sort
number in kill runlevels. We will discuss with upstream how this may be done.

Anyway, a splash screen for a much quicker shutdown becomes less useful :)

Thanks, Kel.