On Sun, Nov 26, 2006 at 06:59:00PM +0100, Roland Rosenfeld wrote: > Marc Haber schrieb am Dienstag, den 21. November 2006: > > Package: file-rc > > Version: 0.8.10 > > Severity: wishlist > > > the -d option to /etc/init.d/rc turns the script into a no-op due to > > the following code: > > > > # Execute the commands collected above > > if [ $debug -eq 1 ] > > then > > echo "$CMDLIST" > > else > > (trap - INT QUIT TSTP; sh -c "$CMDLIST") > > fi > > Correct. That's what I understand by "debug", it gives me the chance > to find out what rc would do without the risk to corrupt the system by > really executing the init scripts. Instead the init script CMDLIST is > only printed out.
I'd call that --dry-run or --no-op. Usually, --debug means "do your job in an explicitly verbose way". > That's exactly what I need the debug mechanism for. > > > Please provide an option that will give debug output while still doing > > something useful. > > Where should this be good for? For example, to find out which part of the init process triggers certain kernel messages or syslog entries. This is arguably a bug in an init script, but it would be great if file-rc would be an aid in finding out which init script is at fault. I think that I filed this bug while trying to learn about how the init process for a system with crypto-filesystems works. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
