Skip to content

The "ff_debug" Command

The ff_debug command in ChromeOS manages debug tags and logging levels for flimflam, the network management system. This section explains how to use this debugging tool effectively.

Command Overview

The basic syntax for the command is: bash ff_debug [<tag_expression>] [--level <level>] [--persist] ff_debug --help ff_debug --reset ff_debug --list_valid_tags

Understanding Debug Tags

Tag Expressions

The command uses boolean notation: - + adds a debug tag - - removes a debug tag - Tags without operators replace existing tags

Debug Levels

  • Level 4 (LOG_FATAL): Most critical only
  • Level 0 (LOG_INFO): Standard information
  • Levels below 0: Verbose logging (SLOG)

Using the Command

Basic Operations

  1. View current settings: bash ff_debug

  2. List valid tags: bash ff_debug --list_valid_tags

  3. Reset all settings: bash ff_debug --reset

Tag Management

  1. Set specific tags: bash ff_debug network+wifi

  2. Modify existing tags: bash ff_debug +network-service

Log Level Control

  1. Set log level: bash ff_debug --level 0

  2. Enable verbose logging: bash ff_debug --level -4

Persistent Settings

  1. Save configuration: bash ff_debug [options] --persist

Best Practices

Debug Configuration

  1. Initial Setup
  2. Check current settings
  3. List available tags
  4. Plan debug strategy

  5. Consider persistence

  6. Tag Selection

  7. Choose relevant tags
  8. Consider combinations
  9. Plan modifications
  10. Document changes

Log Management

  1. Level Selection
  2. Match debugging needs
  3. Consider volume
  4. Monitor impact

  5. Adjust as needed

  6. Resource Usage

  7. Watch storage usage
  8. Monitor performance
  9. Check system impact
  10. Manage log size

Common Use Cases

Network Troubleshooting

  1. General Debugging
  2. Set appropriate tags
  3. Adjust log levels
  4. Monitor output

  5. Analyze results

  6. Specific Issues

  7. Target relevant tags
  8. Focus debugging
  9. Collect evidence
  10. Document findings

Safety Considerations

System Impact

  1. Performance
  2. Log volume
  3. Storage usage
  4. Processing overhead

  5. Memory impact

  6. Resource Management

  7. Monitor usage
  8. Clean up logs
  9. Reset when done
  10. Manage persistence

Troubleshooting

Common Issues

  1. Configuration Problems
  2. Invalid tags
  3. Level conflicts
  4. Persistence issues

  5. Reset failures

  6. Resolution Steps

  7. Check valid tags
  8. Verify syntax
  9. Reset settings
  10. Rebuild configuration