Re: [RFC] how to get the size of a malloc(9) block ?

2013-12-05 Thread jb
jb jb.1234abcd at gmail.com writes: ... So far, the options could be as follows: - realloc_flags(p, s, option) where option is one or a combination (where appropriate) of: REALLOCF_ANY- default (move or no-move; regular realloc

Re: [RFC] how to get the size of a malloc(9) block ?

2013-12-02 Thread jb
()) REALLOCF_NO_MOVE- no-move REALLOCF_ELASTIC- combined with REALLOCF_NO_MOVE REALLOCF_FORCE - combined with REALLOCF_NO_MOVE REALLOCF_FALLBACK_ANY - combined with REALLOCF_NO_MOVE or its derivatives like REALLOCF_ELASTIC, etc jb

Re: [RFC] how to get the size of a malloc(9) block ?

2013-12-02 Thread jb
-and-improved memory management function, admittedly being many OS' and libraries' Achilles' heel :-) jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current

Re: [RFC] how to get the size of a malloc(9) block ?

2013-12-01 Thread jb
teenagers to be abstinent ... http://www.youtube.com/watch?v=SWlbN2b1PGg Good luck ! jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-30 Thread jb
the right thing thru one API call with clear and smart options. If it does 90% of what we would ideally want, then the job is done. jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-30 Thread jb
Reference to realloc(): http://www.cplusplus.com/reference/cstdlib/realloc/ jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-29 Thread jb
, and maintainable API. Note that malloc_usable_size() is a GNU C Library extension, not part of Single UNIX Specification. jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-29 Thread jb
-empowering API. No magic, no hacks. So, how about Request-for-Enhancement to GNU C lib, and the ugly hacks will disappear quickly. jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-28 Thread jb
/Articles/319686/ Result ? The same code works here, but may not elsewhere. It follows, you should remove malloc_usable_size() from user space instead. jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-28 Thread jb
the *requested size* programmatically, it is its business to do it and it can be done very easily. Some of these guys got it perfectly right: http://stackoverflow.com/questions/5813078/is-it-possible-to-find-the-memory-allocated-to-the-pointer-without-searching-fo jb

Re: brigding between two interfaces

2013-10-08 Thread jb
://www.freebsd.org/doc/handbook/network-bridging.html jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

10-CURRENT - LOR (lock order reversal)

2013-09-18 Thread jb
Hi, these represent machine lockups, if not false positives. http://www.freebsd.org/cgi/query-pr.cgi?pr=182139cat= jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail

10-alpha1 iso does not boot

2013-09-14 Thread jb
Hi, FreeBSD-10.0-ALPHA1-i386-disc1.iso Verified checksum. I can not boot from CD-RW at all - it does not seem to be recognized. Anybody else has similar experience ? jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman

Re: 10-alpha1 iso does not boot

2013-09-14 Thread jb
Thomas Mueller mueller6724 at bellsouth.net writes: FreeBSD-10.0-ALPHA1-i386-disc1.iso Verified checksum. I can not boot from CD-RW at all - it does not seem to be recognized. Anybody else has similar experience ? jb Is your CD-RW not recognized even before it tries to boot

Re: 10-alpha1 iso does not boot

2013-09-14 Thread jb
Glen Barber gjb at FreeBSD.org writes: ... Can you try the 20130907 -CURRENT snapshot here? http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/i386/10.0/ Glen OK. That worked out. jb ___ freebsd-current@freebsd.org mailing list http

Re: prompt w/ uid 0 for cshrc

2012-11-19 Thread jb
Eitan Adler lists at eitanadler.com writes: On 18 November 2012 18:44, Mateusz Guzik mjguzik at gmail.com wrote: Just take user name from id -nu. While that does provide the $user value I want, id is in /usr/bin/ which may not be mounted. /rescue/id jb

Re: Using TMPFS for /tmp and /var/run?

2012-04-03 Thread jb
jb jb.1234abcd at gmail.com writes: ... There are memory management subsystem considerations against utilizing tmpfs (memory + swap) for /tmp: ... - Out-of-Memory (OOM) killer Due to it, on heavy loaded systems processes dying on memory pressure. - Pterodactyl The next MM subsystem

Re: Using TMPFS for /tmp and /var/run?

2012-04-02 Thread jb
jb jb.1234abcd at gmail.com writes: ... Chuck Burns brea...@gmail.com 1:01 AM (16 hours ago) My experiences with using tmpfs as /tmp -- It works fine. until it doesn't. I've had mountpoints run out of space, checked df and the mountpoint had been reduced to something

Re: Using TMPFS for /tmp and /var/run?

2012-04-01 Thread jb
is not called for, regardless of memory plus swap sizes. jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Using TMPFS for /tmp and /var/run?

2012-03-30 Thread jb
for these purposes. How do they overcome restrictions of the size or not flloding RAM and/or swap? ... Read it before you make up your mind (there are real issues to consider): http://fedoraproject.org/wiki/Features/var-run-tmpfs http://fedoraproject.org/wiki/Talk:Features/var-run-tmpfs jb

Re: Using TMPFS for /tmp and /var/run?

2012-03-30 Thread jb
differently about /tmp even as part of / fs beeing bombed by mega-size files, and /tmp as /tmpfs (main memory plus swap) getting full or even reaching some preset value and having some priority job or its data or caches being swapped. jb ___ freebsd-current

Re: Updating the tuning man page

2012-03-27 Thread jb
economy_cx_lowest=C2 performance_cpu_freq=HIGH Test: - - measure dev.cpu.0.freq - measure dev.cpu.0.freq during compilation - measure dev.cpu.0.freq while disk quiet 'top' to report near 100% idle - measure dev.cpu.0.freq after few seconds jb ___ freebsd

Re: Double free() in libc or gdb ?

2012-03-13 Thread jb
-lfirst -L. -o test export LD_LIBRARY_PATH=$PWD gdb ./test ... What is your toto.c (source code) ? What about your main.c in compilation ? jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd

Re: SU+J and fsck problem ?

2012-03-11 Thread jb
. But, is there any debugging method I as a user can utilize to collect specific info that could aid devs ? jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current

SU+J and fsck problem ?

2012-03-10 Thread jb
comments before I file a PR# ? jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: revisiting tunables under Safe Mode menu option

2012-03-02 Thread jb
drive, or if you need to reconfigure a service that is preventing your computer from starting properly. This functionality is indeed similar to Single User Mode, but after further considerations it may be different under Safe Mode. jb ___ freebsd

Re: negative group permissions?

2012-02-29 Thread jb
appended a relevant comment. Also, Linux distros (if you can swallow it ...) also disallowed it due to sec reason, but in a clumsy way by making sure the exec permission is turned off in a package install script. jb ___ freebsd-current@freebsd.org mailing

Re: negative group permissions?

2012-02-29 Thread jb
Jason Hellenthal jhellenthal at dataix.net writes: On Wed, Feb 29, 2012 at 08:54:20AM +, jb wrote: 0641 ? Are you sure ? Not at all ;) Checking negative group permissions: 70834 -rw-rx 1 root daemon 4 Feb 21 12:54:02 2012 /var/spool/output/lpd/.seq

Re: negative group permissions?

2012-02-29 Thread jb
, then the periodic sripts need to be changed to ignore this file. The periodic script is OK. Here is the author's view: http://lists.freebsd.org/pipermail/freebsd-hackers/2010-October/033256.html jb ___ freebsd-current@freebsd.org mailing list http

Re: negative group permissions?

2012-02-29 Thread jb
jb jb.1234abcd at gmail.com writes: ... I would suggest (if you can) that you change the .seq permissions to 0664 and watch what happens to it - the purpose is to narrow down who/what changed its mode. Some history. logs. and some ad hoc watch script would do it. Take a look at notify

Re: negative group permissions?

2012-02-29 Thread jb
/var/spool/output/lpd/.seq #! /usr/local/bin/bash touch /tmp/jb-test-`echo $$` # ls -al /var/spool/output/lpd/.seq -rw-rx 1 root daemon 54 Feb 29 17:05 /var/spool/output/lpd/.seq # /var/spool/output/lpd/.seq # # ls /tmp/jb* /tmp/jb-test-61789 # chmod 0640 /var/spool/output/lpd/.seq # ls

Re: negative group permissions?

2012-02-29 Thread jb
for a commiter to handle than just finding and changing the only occurrance of 0661 in lpr.c.) Yes, that's what we suggested, in PR filed as well. Let's change lpr.c so that the .seq create permission is 0664. jb ___ freebsd-current@freebsd.org mailing list

Re: negative group permissions?

2012-02-28 Thread jb
for risque condition like ! -perm +010 -and -perm +001 The file should not be executable, according to its purpose. So the lpr.c should be changed from if ((fd = open(buf, O_RDWR|O_CREAT, 0661)) 0) { to if ((fd = open(buf, O_RDWR|O_CREAT, 0660)) 0) { File a bug report. jb