On 08/10/14 11:07, David Carlier wrote:
Hi all.
I ve made a first draft of a new geolocalization service available here
https://github.com/devnexen/geoloc
which can be used by some other daemons. In short terms, it can gives
geolocalization informations (country code, isp...) from an ip
On 08/10/14 14:28, Jérémie Courrèges-Anglas wrote:
Gustav Fransson Nyvell gus...@nyvell.se writes:
[...]
No. You begin with an RFC.
Really? Besides, an RFC for what, imsg communication?
Again I can't see the point of your posts, and I'm not alone.
I was under the impression
Hi,
Something that has been in my eye for a while; how about those users and
groups?
$ cat /etc/passwd|wc -l
56
$ cat /etc/group |wc -l
75
Maybe one group for write access to /var, one for /etc, etc?
//Gustav
--
This e-mail is confidential and may not be shared with anyone
On 07/15/14 23:55, Philip Guenther wrote:
On Tue, Jul 15, 2014 at 6:20 AM, Gustav Fransson Nyvell
gus...@nyvell.se mailto:gus...@nyvell.se wrote:
On 07/15/14 11:13, Peter Hessler wrote:
On 2014 Jul 15 (Tue) at 10:25:49 +0200 (+0200), Gustav
Fransson Nyvell wrote
On 07/16/14 10:31, Stuart Henderson wrote:
On 2014/07/16 09:53, Gustav Fransson Nyvell wrote:
Hm, no, .xinitrc itself is the process that calls fork etc since it uses a
lib that does this.
Do you mean that you have replaced .xinitrc, which is documented as a
file that should be a shell script
On 07/16/14 10:31, Philip Guenther wrote:
On Wed, Jul 16, 2014 at 2:53 AM, Gustav Fransson Nyvell
gus...@nyvell.se mailto:gus...@nyvell.se wrote:
On 07/15/14 23:55, Philip Guenther wrote:
On Tue, Jul 15, 2014 at 6:20 AM, Gustav Fransson Nyvell
gus...@nyvell.se mailto:gus
Oh, I see, that's exactly what's happened: you've hacked ksh to call a
library that forks and your .xinitrc stopped working as a result.
Doctor, it hurts when I poke myself with a fork()
So don't do that!
Philip Guenther
No wonder you don't have time to code.
--
This e-mail is
On 07/15/14 09:48, Philip Guenther wrote:
When the process that's executing your .xinitrc exits, startx/xinit
will shutdown the X server and then itself exit, taking you back to
the non-X shell prompt. Your .xinitrc should end with execution on
some program which will not exit until you want
On 07/15/14 11:13, Peter Hessler wrote:
On 2014 Jul 15 (Tue) at 10:25:49 +0200 (+0200), Gustav Fransson Nyvell wrote:
:On 07/15/14 09:48, Philip Guenther wrote:
:When the process that's executing your .xinitrc exits, startx/xinit
:will shutdown the X server and then itself exit, taking you back
Hi,
Bit of a programming question/inquiry...
I'm looking at 5.5-current. I'm forking inside a lib and I want to
change the forks cmd or argv[0]. I mean, what you see as command in ps
or top. I've looked at setproctitle. And I lurked around kvm_getprocs
and kvm_getargv, but these functions
On 06/23/14 05:04, Philip Guenther wrote:
On Tue, Jun 17, 2014 at 3:45 PM, Gustav Fransson Nyvell
gus...@nyvell.se mailto:gus...@nyvell.se wrote:
I want to alert you to this strange observation.
$ sysctl -a
...
hw.cpuspeed=3101
hw.setperf=100
...
This on an Intel
Hi,
I want to alert you to this strange observation.
$ sysctl -a
...
hw.cpuspeed=3101
hw.setperf=100
...
This on an Intel i7 3920XM. Rated for 3.8GHz when running 100%.
3101 would mean 3.1GHz and hw.setperf=100 means it should/must run at 100%.
//Gustav
12 matches
Mail list logo
