emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

zcip: use bb_error_msg for logging, not bb_info_msg

Browse Source 
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
Denys Vlasenko 2016-03-30 16:22:13 +02:00
parent 066e76befe
commit cde1199e01
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
networking/zcip.c
View File

@ -176,7 +176,7 @@ static int run(char *argv[3], const char *param, uint32_t nip)
xsetenv("ip", addr);
fmt -= 3;
}
bb_info_msg(fmt, argv[2], argv[0], addr);
bb_error_msg(fmt, argv[2], argv[0], addr);
status = spawn_and_wait(argv + 1);
if (status < 0) {
@ -317,7 +317,7 @@ int zcip_main(int argc UNUSED_PARAM, char **argv)
#if BB_MMU
bb_daemonize(0 /*was: DAEMON_CHDIR_ROOT*/);
#endif
bb_info_msg("start, interface %s", argv_intf);
bb_error_msg("start, interface %s", argv_intf);
}
// Run the dynamic address negotiation protocol,