Package: sysvinit Version: 2.86.ds1-54 Severity: wishlist
hi, sorry to bother, but here's a snipet of out of box thinking: instead of setting the number of starting/killing of each init.d entry, i'd suggest each init.d script should name the processes it needs to run in order to be started. a list for each runstate may also help. from here, package dependencies may be also deduced, like with shlibs. anyway, guessing the correct number for a new package is highly problematic. an user may alter the order by adding processes to the list in a script. at init time, a scan of the dependencies should generate up to a few lists of processes that are unrelated to each other, that may be run as threads, to save time. best regards, alex -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysvinit depends on: ii initscripts 2.86.ds1-54 Scripts for initializing and shutt ii libc6 2.7-6 GNU C Library: Shared libraries ii libselinux1 2.0.59-1 SELinux shared libraries ii libsepol1 2.0.11-1 Security Enhanced Linux policy lib ii sysv-rc 2.86.ds1-54 System-V-like runlevel change mech ii sysvinit-utils 2.86.ds1-54 System-V-like utilities sysvinit recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
