print commands with full log in init.rc

5,425 views
Skip to first unread message

msgboard

unread,
Oct 15, 2010, 4:12:23 PM10/15/10
to android-platform
Dear all,

I am porting android froyo on arm platform. I want init.rc to print
the command it executes while the kernel boots. I am already printing
verbose log messages by changing the loglevel 3 to loglevel 15 at the
start of init.rc.
Please let me know if there are any other commands which will increase
the verbosity, especially I want to be able to print the actual
command which is executed.

thank you for your time

Android Enthusiast

József Király

unread,
Oct 15, 2010, 4:26:26 PM10/15/10
to android-...@googlegroups.com
So basically you want to get the standard Linux on-boot kernel log
showed, what was present in the first builds of Android (before the
cylon-eye animation)? AFAIK, editing the loader source it is possible
(it has a switch what controls just the feature you want)

2010/10/15, msgboard <msgboa...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platfo...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.
>
>

msg board

unread,
Oct 15, 2010, 4:31:02 PM10/15/10
to android-...@googlegroups.com
Hi Jozef
thank you for your reply
 
well... I am already gettting the stardard linux on-boot kernel log. In my case, when the kernel boots, it loads a ramdisk, which contains the init.rc script, this script starts the android framework. I want all the commands in init.rc script to be printed
 


 
2010/10/15 József Király <foni...@gmail.com>

József Király

unread,
Oct 15, 2010, 5:00:53 PM10/15/10
to android-...@googlegroups.com
Hello,

First, it is Jozsef (or Joseph, if you prefer this one)

Second. I know that init.rc initializes the framework, but that should
be posted in the main terminal too. If it isn't then it must use a
separate thread of sh, what AFAIK can not be called for it's content.
Maybe writing a collector daemon what runs before everything and
manages an output list (what is shown onscreen, as a log) would solve
this. But that's a huge maybe!


2010/10/15, msg board <msgboa...@gmail.com>:

>> > android-platfo...@googlegroups.com<android-platform%2Bunsu...@googlegroups.com>


>> .
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-platform?hl=en.
>> >
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "android-platform" group.
>> To post to this group, send email to android-...@googlegroups.com.
>> To unsubscribe from this group, send email to

>> android-platfo...@googlegroups.com<android-platform%2Bunsu...@googlegroups.com>

w wylhistory

unread,
Oct 16, 2010, 10:32:43 PM10/16/10
to android-...@googlegroups.com
you can see the process of init.rc in the codes of init.c;


2010/10/16 József Király <foni...@gmail.com>

Pavan Savoy

unread,
Oct 16, 2010, 10:38:36 PM10/16/10
to android-...@googlegroups.com
How about starting all processes with logwrapper utility and also
starting logcat as service in
itself in the init.rc?
so what ever would have been compiled with DEBUG macro or variable
will be shown ...

--
--Pavan Savoy

Deva R

unread,
Oct 19, 2010, 1:31:41 PM10/19/10
to android-...@googlegroups.com

you can modify init.c to monitor each step on android initial boot.

if interested in native library/app prints, try below..

service logcat /system/bin/logcat -f /dev/kmsg 
       oneshot 


-- 
Regards,
Deva


Reply all
Reply to author
Forward
0 new messages