- Goals
- User guide
- History
- Application testing list
- Getting Started
- Hardware Compatibility List
- Hardware requirements
- JNode Commands
- acpi
- alias
- arp
- basename
- beep
- bindkeys
- bootp
- bsh
- bzip2
- cat
- cd
- class
- classpath
- clear
- compile
- console
- cpuid
- date
- del
- device
- df
- dhcp
- dir
- dirname
- disasm
- echo
- edit
- eject
- env
- exit
- gc
- grep
- gzip
- halt
- help
- hexdump
- history
- ifconfig
- java
- kdb
- leed, levi
- loadkeys
- locale
- log4j
- ls
- lsirq
- man
- memory
- mkdir
- mount
- namespace
- netstat
- onheap
- page
- ping
- plugin
- propset
- pwd
- ramdisk
- reboot
- remoteout
- resolver
- route
- rpcinfo
- run
- startawt
- syntax
- tar
- tcpinout
- thread
- time
- touch
- unzip
- utest
- vminfo
- wc
- zip
- JNode GUI
- JNode Shell
- Performance
- Status
- Classlib developers guide
- Developer guide
- Tester guide
- Porting guide
- Blogs
- Project development
- Glossary
- Proposals
- FAQ
- Papers & presentations
- References
- Research
log4j
console
Synopsis | ||
log4j | --list | -l | list the current log4j Loggers |
log4j | <configFile> | reloads log4j configs from a file |
log4j | --url | -u <configURL> | reloads log4j configs from a URL |
log4j | --setLevel | -s <level> [ <logger> ] | changes logging levels |
Details | ||
The log4j command manages JNode's log4j logging system. It can list loggers and logging levels, reload the logging configuration and adjust logging levels.
The first form of the log4j command list the currently defined Loggers and there explicit or effective logging levels. An effective level is typically inherited from the "root" logger, and is shown in parentheses. The second and third forms of the log4j command reload the log4j configurations from a file or URL. The final form of the log4j command allows you to manually change logging levels. You can use completion to see what the legal logging levels and the current logger names are. If no <logger> argument is given, the command will change the level for the root logger. |