Re: C++ Memory Profiling/Debugging
Hi Lou, Thanks - I'll give it a spin. I read with some reservation on http://dmalloc.com/: Dmalloc is not as good with C++ as C because the dynamic memory routines in C++ are new() and delete() as opposed to malloc() and free(). Since new and delete are usually not used as functions but rather as x = new type, there is no easy way for dmalloc to pass in file and line information unfortunately. The `libdmallocxx.a' library provides the file `dmallocc.cc' which effectively redirects new to the more familiar malloc and delete to the more familiar free. I'll give it a go anyway. Wonder if there is a C++ friendly debug tool out there... Thanks, David On Sat, 21 Feb 2004, Louis LeBlanc wrote: On 02/21/04 12:48 AM, David Carter-Hitchin sat at the `puter and typed: Hi, Does anyone out there know a good C++ memory profiling/debugging tool for FBSD? I'm looking for a tool like valgrind or purify. I grepped around in the ports directory and I found ElectricFence and mprof but these seem to be for C only (as they refer exclusively to malloc free). bohem-gc sounds like the kind of package I'm after - but I thought I ask in case anyone has better ideas... ? devel/dmalloc is pretty good. I'm using it with C on Solaris, but all you do is basically link its library into your process, set a few environment variables, and it will dump a complete list of statistics, based on the values of the environment variables. The most valuable statistic is the origin of every single memory allocation that is not freed. Simply track those made by your code (file name and line number of the malloc are given) and fix them. I found it MUCH easier to integrate and use than Efence or Purify. If your process dynamically allocates memory that isn't intended to be freed, like for internal structure allocation through the life of the process, you might include a routine that frees such pointers in your cleanup process. I have a number of things I have to clear that aren't intended to be freed during the life of the process, so I simply added them within a conditional precompiler block that only gets compiled when I'm building a memory debuggable version. You wouldn't believe the memory leaks I found in (someone else's) production code with this tool. HIGHLY recommended. Good luck. Please cc me on any replies - I had to drop out of this list sometime ago as the sheer volume was killing my mailbox... I know what you mean . . . Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Unless hours were cups of sack, and minutes capons, and clocks the tongues of bawds, and dials the signs of leaping houses, and the blessed sun himself a fair, hot wench in flame-colored taffeta, I see no reason why thou shouldst be so superfluous to demand the time of the day. I wasted time and now doth time waste me. -- William Shakespeare ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
C++ Memory Profiling/Debugging
Hi, Does anyone out there know a good C++ memory profiling/debugging tool for FBSD? I'm looking for a tool like valgrind or purify. I grepped around in the ports directory and I found ElectricFence and mprof but these seem to be for C only (as they refer exclusively to malloc free). bohem-gc sounds like the kind of package I'm after - but I thought I ask in case anyone has better ideas... ? Please cc me on any replies - I had to drop out of this list sometime ago as the sheer volume was killing my mailbox... Thanks, David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_info: read_plist: bad command '@conflicts acroread-3*'
Hi Lowell,
Thanks for your help here... my short question is now How can I
completely refresh my pkg_* suite of tools (apart from
ports/sysutils/pkg_install)? The background is below.
On Tue, 9 Dec 2003, Lowell Gilbert wrote:
David Carter-Hitchin [EMAIL PROTECTED] writes:
Anyone got a clue why this is happening? Should I pkg_delete acroread-3
and reinstall? I googled this one with no luck.
I don't think acroread-3 has been in the ports system in quite some
time. I think the 'conflicts' support post-dates it, so if you remove
it and install a newer acroread port, the problem should go away.
Unfortunately this is not a simple as that.
acroread-5.08/+CONTENTS is actually the file with the offending line
@conflics acroread-3*, so my first thought was hey, acrobat 5 is not
*that* old, I don't want to remove that. So, I thought I'd try a little
hack; made a backup of +CONTENTS (with pico actually, couldn't figure out
why 'vi \+CONTENTS' and suchlike variants were not working.. a digression
I haven't got time for now :-) and removed the conflicts line; hey
presto! the pkg_info command progressed beyond the point it was getting
stuck on before. It then barfed in the same way on another package (which
happened to be reasonably old), so I edited that one's +CONTENTS and again
pkg_info went further... however it now stuck on linux-base which was
installed less than a month ago... suspicious...
Hmm... time to google again. I turned up this recent reply to a post to
this list from Erik Trulsson:
And that still doesn't help me figure out why the packages are not
installing? I have not had problems installing packages up until I've
tried to update the ports collection.
{error}
[EMAIL PROTECTED]:/apps/pkgs] pkg_add openssh-portable-3.7.1p2.tgz
pkg_add: bad command '@conflicts openssh-3.*'
[EMAIL PROTECTED]:/apps/pkgs] pkg_add openssh-3.6.1_5.tgz
pkg_add: bad command '@conflicts openssh-portable-*'
{/error}
Because the packages in question rely on a feature (the @conflicts
directive in this case) that the pkg_add(1) command shipped with
FreeBSD 4.0 does not know how to handle.
To handle packages that have been built from an up-to-date ports
collection, you usually need up-to-date versions of the pkg_* tools.
(It seems as if you can get such via the sysutils/pkg_install port, but
I haven't tested that myself, so I don't know how well it works.)
Well, guess what? I've recently (couple of months ago) upgraded from FBSD
4.2 to 4.8 and so there must be something still archaic about my pkg_*
tools or underlying libraries that is causing this. The upgrade generally
went without any problems and everything (200+ packages) are working ok
(apart from some annoying TeX type errors and this pkg problem).
I have also installed sysutils/pkg_install (in fact I had originally tried
that under 4.2) and have recently done a reinstall too. I managed to get
pkg_version to report:
pkg_install-20030714_1 = up-to-date with port
Can anyone say what needs refreshing on my FBSD? I ktrace'd pkg_info and
listed all the libraries I could see it using and they seem up to date:
-r-xr-xr-x 3 root wheel 10168 Nov 16 21:23 /usr/bin/perl
-r--r--r-- 1 root wheel 577872 Nov 16 21:21 /usr/lib/libc.so.4
-r--r--r-- 1 root wheel 577872 Nov 16 21:21 /usr/lib/libc.so.4
-r--r--r-- 1 root wheel 28432 Nov 16 21:21 /usr/lib/libcrypt.so.2
-r--r--r-- 1 root wheel 28432 Nov 16 21:21 /usr/lib/libcrypt.so.2
-r--r--r-- 1 root wheel 117024 Nov 16 21:21 /usr/lib/libm.so.2
-r--r--r-- 1 root wheel 117024 Nov 16 21:21 /usr/lib/libm.so.2
-r--r--r-- 1 root wheel 117024 Nov 16 21:21 /usr/lib/libm.so.2
-r--r--r-- 1 root wheel 34092 Nov 16 21:21 /usr/lib/libmd.so.2
-r--r--r-- 1 root wheel 34092 Nov 16 21:21 /usr/lib/libmd.so.2
-r--r--r-- 1 root wheel 614824 Nov 16 21:23 /usr/lib/libperl.so.3
-r--r--r-- 1 root wheel 32728 Nov 16 21:21 /usr/lib/libutil.so.3
-r--r--r-- 1 root wheel 32728 Nov 16 21:21 /usr/lib/libutil.so.3
-r-xr-xr-x 1 root wheel 10293 Nov 16 21:23 /usr/libdata/perl/5.00503/Carp.pm
-r-xr-xr-x 1 root wheel9900 Nov 16 21:23 /usr/libdata/perl/5.00503/Cwd.pm
-r-xr-xr-x 1 root wheel 14112 Nov 16 21:23 /usr/libdata/perl/5.00503/Exporter.pm
-r-xr-xr-x 1 root wheel 14112 Nov 16 21:23 /usr/libdata/perl/5.00503/Exporter.pm
-r-xr-xr-x 1 root wheel4320 Nov 16 21:23 /usr/libdata/perl/5.00503/Getopt/Std.pm
-r-xr-xr-x 1 root wheel 81932 Oct 31 01:00 /usr/libexec/ld-elf.so.1
-r-xr-xr-x 1 root wheel 16551 Nov 16 21:26 /usr/sbin/pkg_version
-r-xr-xr-x 1 root wheel 16551 Nov 16 21:26 /usr/sbin/pkg_version
Obviously something needs refeshing... but what? If this is a documented
somewhere, then I'm sorry about the bandwidth wastage, but I've searched
extensively on google and freebsd.org and the man pages, but I've found
nothing which says this is a known problem, do X and Y to fix it, only
references to other poor souls who were suffering
Re: a technical how to
Hiya,
no-one has mentioned 'head' yet:
head -100 file newfile
to save the first 100 lines of file into newfile.
You can also use a combination of head and tail to take a portion of the
file, e.g:
head -100 file | tail -3 newfile
to save off lines 98,99 and 100 of file into newfile. I've known this to
be useful when trying to extract certain lines from mammoth files.
If, by a certain point you meant, for example, up to some general regex
then you could employ some perl:
cat file | perl -e 'while () { exit if /REGEX/; print }' newfile
I know you can do similar things in sed and awk, but I don't know the
syntax off the top of my head, and don't have my notes to hand.
David
On Tue, 9 Dec 2003, Charles Swiger wrote:
On Dec 8, 2003, at 8:51 PM, homeyra g wrote:
Here is the question: How to truncate a file from the
begining to a certain point in the file?
The question is whether this file is ASCII text so line-based tools
(such as tail) work, or whether you are truncating a binary file, in
which case split -b is probably a better bet.
If you've got a logfile named /var/log/messages, and you want to
truncate that to the last 100 lines:
mv /var/log/messages /var/log/messages.$$
tail -100 /var/log/messages.$$ /var/log/messages
rm -f /var/log/messages.$$
Use wc -l and grep -n to identify where to truncate the file if
it's not a fixed size that you want...
--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a technical how to
no-one has mentioned 'head' yet:
head -100 file newfile
to save the first 100 lines of file into newfile.
You can also use a combination of head and tail to take a portion of the
file, e.g:
head -100 file | tail -3 newfile
to save off lines 98,99 and 100 of file into newfile. I've known this to
be useful when trying to extract certain lines from mammoth files.
If, by a certain point you meant, for example, up to some general regex
then you could employ some perl:
cat file | perl -e 'while () { exit if /REGEX/; print }' newfile
I know you can do similar things in sed and awk, but I don't know the
syntax off the top of my head, and don't have my notes to hand.
David
On Tue, 9 Dec 2003, Charles Swiger wrote:
On Dec 8, 2003, at 8:51 PM, homeyra g wrote:
Here is the question: How to truncate a file from the
begining to a certain point in the file?
The question is whether this file is ASCII text so line-based tools
(such as tail) work, or whether you are truncating a binary file, in
which case split -b is probably a better bet.
If you've got a logfile named /var/log/messages, and you want to
truncate that to the last 100 lines:
mv /var/log/messages /var/log/messages.$$
tail -100 /var/log/messages.$$ /var/log/messages
rm -f /var/log/messages.$$
Use wc -l and grep -n to identify where to truncate the file if
it's not a fixed size that you want...
--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Terminal setting
Greetings, There are (at least) two sides to this problem. Firstly you must ensure the FreeBSD is using the right keymap for your country and keyboard. For example to get my standard UK keyboard working I had to put the following line in my configuration: /etc/rc.conf.local:keymap=uk.iso.kbd (and reboot) Alternate keymaps are stored under: /usr/share/syscons/keymaps I don't see one that begins with ir, but you may find one close enough, and you can always make your own. They are ascii files so you can read how they're structured. man keyboard would be an admirable starting place to read about such things. Once I had done this all those really useful characters like # @ \ and ~ were in the right places on the keyboard (where the keys advertised they were). I also had to tell X about my keyboard: Option XkbLayout uk.iso.kbd (That style of option may be different in your version of X - check the man pages - they've changed during the last major release). If that doesn't fix your problem (which it may do) then we need to know which terminal program you are using - is it the console or an xterm window within X? If its an X program then it could be the bindings, which can be changed. On *any* terminal you can normally fix the back space by doing this: stty erase [Backspace][Return] That's two keystrokes at the end there, not the literal characters '[ B a c...' This has the effect that the terminal settings will delete a char from your current line when you hit the backspace key. In Emacs you can nearly always work around not having the meta key by typing ESC-x (Emacs then kindly prompts with M-x) Syntax highlighting is another kettle of fish. First check is to ensure your terminal supports colour - can you see any colours of any description there (such as the FreeBSD install screens)? Emacs you explicity have to switch it on (Help | Options | Global Font Lock..) - maybe on another version you had that was set in your $HOME/.emacs file. vim I got that working once, but I forget how off the top of my head... I'm not really a fan of vim (except for very large files which vim handles so much better than vi - in fact it handles them full stop, vi just dies after a certain size). HTH David On Wed, 10 Dec 2003, Hossein wrote: Hello; My FreeBSD box is going to serve some young shell users who have begun with Linux. In order to atract them it mustbe as good looking as a Linux system but I am having serious peroblem with my terminal settings. Some vary important keys such as Back Space, home, end and ... don't work in editors such as vim. For example in Emacs the Alt key does not work. Also editors such as vim and Emacs do not show syntax highlighting and so on. Can anybody help me with this problem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using multiple zip disks
from the ZIP FAQ I constructed the following script: [501]-cat makezip.sh #!/bin/sh dd if=/dev/zero of=/dev/da0 count=2 disklabel -Brw da0 auto newfs /dev/da0c HTH David. On Mon, 24 Nov 2003, Charles Howse wrote: Hi, I have an external USB Iomega Zip 250 drive that is working properly after I configured it using sysinstall. I have added an entry to fstab that allows me to just enter mount /zip to mount it. /dev/da0s1e /zipufs rw,noauto 0 0 The problem is that I have more than one zip disk that I would like to use. I have some zip 100's and some zip 250's. The only disk that has a ufs filesystem on it is the one that was in it when I configured it, a zip 100. What is the proper way in 4.8 to prepare my other disks so that I can insert any of them, regardless of the size, and just enter mount /zip? I'm thinking use sysinstall with one of the zip 250's in the drive, configure a new slice, and mount it at /zip2...? Then I would mount /zip2 Then maybe I can just insert one of the zip 100's, and manually put a filesystem on it like I was installing a new HD...? Am I close? Is there a *real* easy way? -- Thanks, Charles http://howse.homeunix.net Random Murphy's Law: The inside contact that you have developed at great expense is the first person to be let go in any reorganization. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pkg_info: read_plist: bad command '@conflicts acroread-3*'
Hail, pkg_info bombs on 4.8-RELEASE: [512]-pkg_info Mesa-3.2.1_1A graphics library similar to SGI's OpenGL ORBit-0.5.17_1 High-performance CORBA ORB with support for the C language WordNet-1.7.1 Dictionaries and thesauri with devel. libraries (C, TCL) an XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using mini/meta-po XFree86-FontServer-4.3.0_2 XFree86-4 font server XFree86-Server-4.3.0_12 XFree86-4 X server and related programs XFree86-clients-4.3.0_5 XFree86-4 client programs and related files XFree86-documents-4.3.0 XFree86-4 documentation XFree86-font100dpi-4.3.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.3.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontCyrillic-4.3.0 XFree86-4 Cyrillic fonts XFree86-fontEncodings-4.3.0 XFree86-4 font encoding files XFree86-fontScalable-4.3.0 XFree86-4 scalable fonts XFree86-libraries-4.3.0_6 XFree86-4 libraries and headers Xaw3d-1.5 A 3-D Athena Widget set that looks like Motif Xft-2.1.2 A client-sided font API for X applications aalib-1.4.r5_1 An ascii art library pkg_info: read_plist: bad command '@conflicts acroread-3*' Anyone got a clue why this is happening? Should I pkg_delete acroread-3 and reinstall? I googled this one with no luck. I'm trying to resolve some nasty problem with teTeX and dvips which were working beautifully before I did a portupgrade -arR :-( I need to know exactly which versions of things are installed before removing them. I'm trying stuff like this: [514]-pkg_delete dvips pkg_delete: no such package 'dvips' installed [515]-pkg_delete dvips-5.76 pkg_delete: package 'dvips-5.76' doesn't have a prefix [516]-pkg_delete print/dvips-5.76 pkg_delete: package 'dvips-5.76' doesn't have a prefix (I'm trying to get dvips-5.92b working without error, which is why I want to remove dvips-5.76). Thanks, David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp link always dials when started with -auto?
Hi, With lots of help from John Chung I eventually fixed this problem - it was because ipv6 was configured. I've disabled that in the kernel (I survived without it for years, so no reason to have it as part of my upgrade). I clocked up about 15 hours trying to debug this problem - that would have been cut down to about 30 mins had this been in the FAQ. Can someone please add this side effect of ipv6 on ppp to FAQ 14.17 or alternatively I am happy to volunteer to do it myself? There again if someone knows a cunning way to make ppp and ipv6 sit happily together that might be a better way forward... Thanks, David. On Sun, 26 Oct 2003, David Carter-Hitchin wrote: Hi FreeBSD'ers, I've just upgraded to 4.9-RC (from 4.2) and I'm really happy with everything except ppp. Whenever I start ppp (with ppp -auto pmdemand) it immediately starts to dial - after connecting it briefly sends and receives a minimal amount of data then sits there idly. One other problem I've got with my upgrade is that I'm getting pam errors: Oct 26 20:26:25 stoat login: no modules loaded for `login' service Oct 26 20:26:25 stoat login: pam_open_session: Permission denied (related?) I've read the ppp faq and this question is covered and it says sendmail is the often the culprit. This rang loud bells as I saw that the more recent version of sendmail has depreciated the 'nodns' feature. So I tried rebooting without sendmail running, but still the same problem. I tried killing off a few daemons including inetd, lpd, usbd.. but no joy. I added log All +tcp/ip to get the full output, but I don't know enough about this stuff to go further. I initially get the following lines in the log: Oct 26 21:17:32 stoat ppp[466]: tun0: TCP/IP: OUT 0: fe80::240:95ff:fe44:3e11 --- ff02::1:ff44:3e11 (72) Oct 26 21:17:32 stoat ppp[466]: tun0: TCP/IP: OUT ICMP: :::135 --- ff02::1:ff44:3e11 (16/64) I've uploaded the rest of the conversation to: http://www.carter-hitchin.clara.co.uk/logs/ppp.log.gz My setup is an isolated workstation (no LAN, occasional dialup). Here are some outputs: [516]-uname -a FreeBSD stoat.clara.net 4.9-RC FreeBSD 4.9-RC #0: Sat Oct 18 13:56:46 BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/STOAT i386 [517]-cat /etc/ppp/ppp.conf default: #set log Phase Chat LCP IPCP CCP tun command set log All ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cuaa0 set speed 115200 set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \\ ATM1 OK \\dATDT\\T TIMEOUT 40 CONNECT enable dns pmdemand: set timeout 300# 3 mintue idle timer (the default) set phone XXX set authname X set authkey XX add default HISADDR# Add a (sticky) default route set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 [68]-cat /etc/resolv.conf domain=stoat nameserver 195.8.69.7 nameserver 195.8.69.12 [69]-cat /etc/hosts ::1 localhost localhost.clara.net 127.0.0.1 localhost localhost.clara.net stoat.clara.net 127.0.0.1 stoat stoat.clara.net 127.0.0.1 carter-hitchin.clara.co.uk I'd really appreciate some help here - I'm stuck in being able to identify precisely what is using the link. Many thanks, David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: problems with LPD
But before this I like to try the netgroup option, where can I begging to read?. man yp David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help With 'find' Syntax
Hi Drew, Find is one of those classic commands for confusing people. One just gets used to it over time. The behaviour of find varies significantly with different unixes under different shells. Which shell are you using? Under bash this command does what you want: find / -mtime 7 -size +1024c -ls -o -ctime 7 -size +1024c -ls the sense here is: find / (-mtime 7 -size +1024c -ls) -o (-ctime 7 -size +1024c -ls) meaning find (i.e. examine all files) from / and either a) print (-ls) files modified exactly 7 days old and greater than size 1024 chars (bytes). or (-o) b) print (-ls) files whose inode creation times are exactly 7 days old and greater than size 1024 chars. If neither a) nor b) are true for a file found under / then it is silently ignored. You may find the following note from man find helpful: # All primaries which take a numeric argument allow the number to be pre- # ceded by a plus sign (``+'') or a minus sign (``-''). A preceding plus # sign means ``more than n'', a preceding minus sign means ``less than n'' # and neither means ``exactly n''. So that is why I put a + in from of 1024 - to find files over 1024 bytes (c). So in your example below: find /usr \( -mtime 6 -ls -size 100 \) -o \( -ctime 6 -ls -size 100 \) -print You are trying to find files that are exactly 100 512k blocks in size. Admittedly the files you found were not of this size and I don't know why they were found - I can replicate this on my machine here, but I don't know why - perhaps it is the file allocation. This is why I chose 1024c instead of block size. (And why is this file listed twice, anyway?) Perhaps because there was a symbolic link pointing to it (as shown by the '2' before the permissions). HTH, David On Fri, 31 Oct 2003, Drew Tomlinson wrote: - Original Message - From: David Carter-Hitchin [EMAIL PROTECTED] To: Drew Tomlinson [EMAIL PROTECTED] Cc: FreeBSD Questions [EMAIL PROTECTED] Sent: Thursday, October 30, 2003 5:55 PM Subject: Re: Help With 'find' Syntax Hi Drew, This should find all files created or modified on 25th October: find / -mtime 6 -ls -o -ctime 6 -ls (As today is 31st October which is 6 days after 25th. You may need to widen your search a little with a seperate search with 7 as the paramter as 6 may not catch files that were created over 6 * 24 hours ago (but were still on the 25th); not sure about that). Thank you for your reply. I tried your suggestion and it seems to get what I want. However there are so many little files that I thought I'd modify the command to: find /usr \( -mtime 6 -ls -size 100 \) -o \( -ctime 6 -ls -size 100 \) -print If I understand the '-size' primary correctly, this means I would find files that are '100 512-byte blocks' in size or '50k'. Yet I still get output like this: 7621552 -r--r--r--1 root wheel 928 Oct 25 15:12 /usr/local/man/man3/pcre_compile.3.gz 7621552 -r--r--r--1 root wheel 928 Oct 25 15:12 /usr/local/man/man3/pcre_compile.3.gz (And why is this file listed twice, anyway?) So I guess my question is how can I find files created or modified on Oct. 25 and are larger than size? Thanks for any help. This is really confusing to me. Drew HTH, David On Wed, 29 Oct 2003, Drew Tomlinson wrote: On October 25, my /usr partition lost nearly 50% of it's available space. This disk hasn't had any significant size changes since I built the system as it basically serves as a gateway. I'm trying to use the find command to determine what may have been written to the disk but am not having any luck. I see primaries such as -atime, -mtime, -ctime, and -newer and have read the man pages but do not understand what the best combination to find those files. Basically how do I use 'find' to show me all file that were created or modified on October 25? I've tried commands such as find /usr \( -newerct 4d \! -newerct 3d \) -print but nothing is returned. Thanks, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help With 'find' Syntax
Hi Drew, This should find all files created or modified on 25th October: find / -mtime 6 -ls -o -ctime 6 -ls (As today is 31st October which is 6 days after 25th. You may need to widen your search a little with a seperate search with 7 as the paramter as 6 may not catch files that were created over 6 * 24 hours ago (but were still on the 25th); not sure about that). HTH, David On Wed, 29 Oct 2003, Drew Tomlinson wrote: On October 25, my /usr partition lost nearly 50% of it's available space. This disk hasn't had any significant size changes since I built the system as it basically serves as a gateway. I'm trying to use the find command to determine what may have been written to the disk but am not having any luck. I see primaries such as -atime, -mtime, -ctime, and -newer and have read the man pages but do not understand what the best combination to find those files. Basically how do I use 'find' to show me all file that were created or modified on October 25? I've tried commands such as find /usr \( -newerct 4d \! -newerct 3d \) -print but nothing is returned. Thanks, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time... lots of odd errors
Hi, Looks like you may have a hardware fault: from /usr/src/sys/kern/kern_clock.c * 0 - every tick, bad hardware may fail with calcru negative... David On Thu, 23 Oct 2003, Heath Volmer wrote: Hopefully this one will get through... I've searched exhaustively for an answer to this question, and can only get answers that aren't entirely clear to me. I'm getting messages like: calcru: negative time of -630883 usec for pid 537(sh). Getting probably 40 or so at boot and an occasional one during use. This a new 5.1 install on an older K6 500Mhz system that was given to me. I have read something about a sysctl command (no good.) Also have seen something about a kernel TIMECOUNTER (I think) config value. I've also seen something about PnP, bios settings, IRQ probs, etc. I'm a bit too new at this to know where to take it. Help! Thanks, Heats ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5406 warnings during buildworld other q's
Hi Kris, Thanks for replying... d) installworld failed the first time as the user 'smmsp' didn't exist. I dutifully followed the advice given in UPGRADE by building and running mergemaster. Second run of installworld also failed - at mergemaster, saying Don't know how to build mergemaster.sh. I'm not sure if I did the right thing, but copying /usr/sbin/mergemaster to the source directory /usr/src/usr.sbin/mergemaster and renaming it to mergemaster.sh, fixed the problem. Can anyone comment on this? = It looks like your buildworld didn't complete before you tried to = installworld it. As far as the process is concerned it definitely completed, and I grepped for errors and found none in the logfile. The last thing buidlworld logged was: chmod 444 freebsd.submit.cf Having done this for the first time, I don't know what the last line should be. Does it say buildworld complete? I checked the timestamp on both ld-elf.so.1 and libm.so.2 and they were built today - anyone know what might have caused this? Do I need to rebuild cvsup, if so how? = This is explained in UPDATING. Ah yes... thanks. Readme.html's. Is that a bug? = No, you told cvsup to delete your ports collection (the ports tree is = not branched). This is also explained in the handbook. DOOF! Won't be doing that again in a hurry. Thanks, David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5406 warnings during buildworld other q's
Hi Free BSDers, Sorry about my question overload here. I've just successfully cvsup'd to -STABLE (I think), done a buildworld, installworld and rebuilt the kernel. Everything seemed to go generally ok but I had a few observations/questions: a) Firstly I had difficulty finding much information about the specific tag I should use in the tag= line in the cvsup file. I can't remember accurately all the places I looked, but it included the handbook, faq, the /usr/share/examples/cvsup/stable-supfile and Greg Lehey's book (3rd ed.). The one place I didn't look was on the website, but I couldn't do that as after a unsuccessful buildworld (with cvsup tag=.), my web browser gave up working at all and just coredumped. Can someone clarify where definitive and up to date information regards the tag entries can be found? In the end I plumped for RELENG_4 (as recommended by the stable-supfile), I've ended up with 4.9-RC - is that a stable version? I was a bit concerned to see someone else on this list mentioned RELENG_4_8, which I understood was the STABLE version so it would be cool to have clarification. b) The first run of buildworld failed as vgrind was not on my system. I hunted down vgrind under /usr/src/usr.bin, built that and ran buildworld successfully a second time. c) buildworld generated 5406 warnings. Some examples are: yppasswdd_server.o(.text+0xba9): warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/ include/opcode/i386.h:1094: warning: initialization discards qualifiers from pointer target type I have uploaded the logs to: http://www.carter-hitchin.clara.co.uk/logs/buildworld.log.gz http://www.carter-hitchin.clara.co.uk/logs/installworld.log.gz Are these warnings normal? Should I run buildworld again? I should note here that I was previously running 4.2 d) installworld failed the first time as the user 'smmsp' didn't exist. I dutifully followed the advice given in UPGRADE by building and running mergemaster. Second run of installworld also failed - at mergemaster, saying Don't know how to build mergemaster.sh. I'm not sure if I did the right thing, but copying /usr/sbin/mergemaster to the source directory /usr/src/usr.sbin/mergemaster and renaming it to mergemaster.sh, fixed the problem. Can anyone comment on this? e) 'cvsup -g -L2 ports-supfile' now generates an error: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp I checked the timestamp on both ld-elf.so.1 and libm.so.2 and they were built today - anyone know what might have caused this? Do I need to rebuild cvsup, if so how? f) At some point (I think after doing a cvsup with tag=RELENG_4 I lost all my ports files - the only files I can see under /usr/ports/*/* are Readme.html's. Is that a bug? Luckily I kept a copy of my ports tree so I'll use that until I can figure out e) above. Many thanks for your help, David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld: bsd.lib.mk line 18: Malformed conditional
Hi All,
Hope someone out there knows about a problem I've run into doing a make
buildworld in /usr/src. The problem seem to be whilst building
rescue/common:
cd /usr/src/rescue/rescue/../../sbin/fdisk
MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue make clean
rm -f fdisk fdisk.o geom_mbr_enc.o fdisk.8.gz fdisk.8.cat.gz
cd /usr/src/rescue/rescue/../../sbin/dhclient
MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue make clean
=== rescue/rescue/common
/usr/src/share/mk/bsd.lib.mk, line 18: Malformed conditional
(defined(SHLIB_NAME) ${SHLIB_NAME:M*.so.*})
/usr/src/share/mk/bsd.lib.mk, line 18: Missing dependency operator
/usr/src/share/mk/bsd.lib.mk, line 22: if-less endif
/usr/src/share/mk/bsd.lib.mk, line 22: Need an operator
make: fatal errors encountered -- cannot continue
uname -a:
FreeBSD stoat.clara.net 4.2-RELEASE FreeBSD 4.2-RELEASE #4: Sun Sep 29
00:27:09 BST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/STOAT
i386
I only recently found out about CVSup, so I'm a bit new to this method. My
update file looks like this:
*default host=cvsup.uk.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
*default compress
src-all
ports-all
doc-all
Did I get something wrong? Or is my 4.2 installation so old that it has no
hope of being upgraded in this way? Not sure if my release= config
means that I get STABLE, CURRENT or something else?
Thanks,
David.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
