On Tuesday 21 October 2008 23:27:33 Matthias Apitz wrote:
> El día Tuesday, October 21, 2008 a las 12:51:22PM +1100, Sarton O'Brien
> escribió:
>
> ...
>
> > You were asking for documentation for _technically_ a 3rd party program
> > included on an embedded system. It makes sense to consult t
hen I wake it up events/0 usually resumes
normal behaviour. The longer it sleeps, the better is rate of success, but
most of the time couple of minutes is enough.
--
View this message in context:
http://n2.nabble.com/-Om2008.9--man-pages---killing-events-0-tp1351870p1359398.html
Sent from
El día Tuesday, October 21, 2008 a las 12:51:22PM +1100, Sarton O'Brien
escribió:
...
> You were asking for documentation for _technically_ a 3rd party program
> included on an embedded system. It makes sense to consult the website of the
> software or (heaven forbid) search for the man
On Monday 20 October 2008 18:57:21 Matthias Apitz wrote:
> El día Monday, October 20, 2008 a las 06:45:26PM +1100, Alex Osborne
escribió:
> > Well of course it's going to be different on FreeBSD -- different kernel
> > -- but the location of the CPU time in /proc is going to be the same as
> > any
> Of course and I was not expecting the man pages installed on the FR.
If you use the Debian distribution, manpages are installed just as on
any other Debian system.
Stefan
___
Openmoko community mailing list
community@lists.openmoko.org
http
> CPU time of a proc? I was thinking in something like 'cat /proc/5/...'
it's hard to believe there should be no python way to access procfs more
generic (not to speak of other languages).
maybe
> http://mail.python.org/pipermail/python-list/2004-December/298171.html
helps?
Matthias Apitz wrote:
> I thing Linux/UNIX goes the wrong way if we depend on Google to lookup
> man pages;
We don't. Well, at least anyone actually running Linux doesn't. Just
typing "man proc" worked for me. ;-) I added the Google link as an
after-thought in case you were running something e
El día Monday, October 20, 2008 a las 06:45:26PM +1100, Alex Osborne escribió:
> Well of course it's going to be different on FreeBSD -- different kernel
> -- but the location of the CPU time in /proc is going to be the same as
> any other system running the Linux kernel (well at least any that's
Matthias Apitz wrote:
>>>
>>> $ man proc
>>
>> By the way, if you don't have them locally:
>>
>> http://www.google.com/search?q=proc+manpage
>
> Don't you think that this answer is too simple?
I thought it was dead easy. Why, what sort of hoops do you prefer to
jump through to find a man page?
http://www.google.com/search?q=man+page+dropbear
its in several places down that list.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
El día Monday, October 20, 2008 a las 11:20:45AM +1100, Alex Osborne escribió:
> Alex Osborne wrote:
> > Matthias Apitz wrote:
> >
> >> how can I ask for the actual
> >> CPU time of a proc? I was thinking in something like 'cat /proc/5/...'
> >> but have no man pages about the /proc layout :-(
>
Alex Osborne wrote:
> Matthias Apitz wrote:
>
>> how can I ask for the actual
>> CPU time of a proc? I was thinking in something like 'cat /proc/5/...'
>> but have no man pages about the /proc layout :-(
>
> $ man proc
By the way, if you don't have them locally:
http://www.google.com/search?q=p
Matthias Apitz wrote:
> how can I ask for the actual
> CPU time of a proc? I was thinking in something like 'cat /proc/5/...'
> but have no man pages about the /proc layout :-(
$ man proc
[...]
/proc/[number]/stat
Status information about the process. This is used by ps(1). It is
define
Hello,
I'm thinking in writing s small script which pops up a box on the FR and
asking for reboot if this proc events/0 run away; the application for
the pop-up could easy be done in Python; how can I ask for the actual
CPU time of a proc? I was thinking in something like 'cat /proc/5/...'
but ha
14 matches
Mail list logo
