altering "maxdsiz" or "datasize" limit ?
Hello, We've been satisfied FreeBSD users for several years at our hosting company. Recently we ran into into a problem where a long running cron script was dying early because it is hitting FreeBSD's data segment size limit of 512 Megs, even though the machine has plenty more memory. I would like to raise this limit, and am currently using FreeBSD 6.2. When I researched this, I first found references to tuning "maxdsiz" in loader.conf, then some pointed out what I found myself this variable is no longer documented and perhaps no longer present in FreeBSD 6.2. I also found that it appears you can report on it and change it with the "limits" command: limits -d 1g That appears to work in the sense that the command is allowed and no error is returned, but then if I run a follow up "limits" report again, I see that no change is reported to have happened. So, how I can actually increase this limit? (Both immediately and persisting through a reboot). Thanks! Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: solution: getting a Motorola Razr V3 to work as a GSM modem on FreeBSD
> On Thu, 5 Nov 2009 13:15:24 -0500, Mark Stosberg wrote: > > For software to send the pages, I use the "gammu" port. > > > > I ran "gammu-config" for the initial setup, and then moved the > > resulting file from /root/.gammurc to the more standard > > location: /etc/gammurc > > FreeBSD separates configuration files for the system (/etc > subtree) and for additional ports (/usr/local/etc subtree), > so /usr/local/etc/gammurc would, in my opinion, be the > correct place for this file. I agree. However, the related man pages didn't reference this option. This seems like a place where the code and docs could use a small patch to work this way on FreeBSD. (Or maybe it already works this way, and the docs don't reflect it). I suppose in my case, I could still move the config file to /usr/local/etc/ and then symlink it from /etc/, which would meet the requirements of the software, and also meet the expectations of someone expecting a standard FreeBSD layout. > Many thanks, Mark, this really sounds interesting and useful, > a very good combination. :-) You are welcome. I have been running a hosting business on FreeBSD since about 1997 and it has worked very well for us. Mark -- http://mark.stosberg.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Specifying only constrained options in /etc/libmap.conf ?
I would like to use /etc/libmap.conf to apply some mappings which only apply to the "darcs" executable. However the man page for "libmap.conf" contains this warning: "WARNING! Constrained mappings must never appear first in the configura- tion file. While there is a way to specify the ``default'' constraint, its use is not recommended." Warning aside, I thought what I would want is the following. Is there a better way? I want to limit the scope of this change because I'm not sure how it will affect the rest of the system, particularly MySQL. [darcs] libpthread.so.1 libthr.so.1 libpthread.so.2 libthr.so.2 libkse.so.3 libthr.so.3 Thanks for your help! Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer m...@summersault.com Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . . ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: named fails to start on boot on FreeBSD 6.1, complains about libxml2.so.5
> Agreed. Bind 9.5 and higher from ports has "XML statistics" support. That > explains the xml and iconv. ldd -a /usr/sbin/named should show you which one > wants libm.so.2 which is from the 4.x days. > If you don't need these statistics, I would suggest turning them off through > make config. This is great feedback. I confirmed the old "compat" dependency is from libxml, and it's true we don't use those XML stats. I like the suggestion of using "make config" to recompile without the stat support, which will remove all the troublesome dependencies for us. Thanks! Mark ldd -a /usr/sbin/named /usr/sbin/named: libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000) libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x283ef000) libm.so.4 => /lib/libm.so.4 (0x284e3000) libc.so.6 => /lib/libc.so.6 (0x284f9000) /usr/local/lib/libxml2.so.5: libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x283ef000) libm.so.2 => /usr/local/lib/compat/libm.so.2 (0x285d1000) Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: named fails to start on boot on FreeBSD 6.1, complains about libxml2.so.5
> > We had problem with "named" starting on boot on a FreeBSD 6.1 server, > > managed > > by /etc/rc.conf. > > > > The startup script failed with errors about shared library "libm.so.2" > > failing > > to load because of something related to libxml2.so.5. > > > > Later, when I then tried starting it via /etc/rc.d/named it worked fine. > > > > I include the following "ldd" output in case it's helpful. What could > > possibly > > be the issue here? > > > >Mark > > > > ### > > > > # ldd /usr/sbin/named > > /usr/sbin/named: > >libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000) > >libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000) > >libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x283ef000) > >libm.so.4 => /lib/libm.so.4 (0x284e3000) > >libc.so.6 => /lib/libc.so.6 (0x284f9000) > >libm.so.2 => /usr/local/lib/compat/libm.so.2 (0x285d1000) > > I also see to LOCAL libraries in it. named is part of base, unless you > compiled and installed the port version and maybe told it to overwrite the > base. > > None of this adds up. > > %ldd /usr/sbin/named > /usr/sbin/named: > libcrypto.so.5 => /lib/libcrypto.so.5 (0x281fe000) > libthr.so.3 => /lib/libthr.so.3 (0x28357000) > libc.so.7 => /lib/libc.so.7 (0x2836a000) > > There's a named on 7.1p4 Thanks for the response. I've now compared this named 'ldd' outfit to another 6.1 install we have that also runs named. It has the exact same file size and version, but slightly different ldd output: -- from the second machine with FreeBSD 6.1 # ldd /usr/sbin/named /usr/sbin/named: libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000) libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000) libz.so.3 => /lib/libz.so.3 (0x283ff000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2840f000) libm.so.4 => /lib/libm.so.4 (0x284fc000) libc.so.6 => /lib/libc.so.6 (0x28512000) XML is still there, but the mention of libm.so no longer points into /usr/local/lib/compat This other FreeBSD user also found the libxml link: https://lists.isc.org/pipermail/bind-users/2008-November/073929.html I also checked "/etc/make.conf" on both machines. They mentioned X11_BASE and Perl... nothing about XML. However, these machines have evolved some over time. Perhaps something with there in the past. It sounds like advisable paths forward include re-compiling or re-installing named. Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
named fails to start on boot on FreeBSD 6.1, complains about libxml2.so.5
We had problem with "named" starting on boot on a FreeBSD 6.1 server, managed by /etc/rc.conf. The startup script failed with errors about shared library "libm.so.2" failing to load because of something related to libxml2.so.5. Later, when I then tried starting it via /etc/rc.d/named it worked fine. I include the following "ldd" output in case it's helpful. What could possibly be the issue here? Mark ### # ldd /usr/sbin/named /usr/sbin/named: libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000) libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x283ef000) libm.so.4 => /lib/libm.so.4 (0x284e3000) libc.so.6 => /lib/libc.so.6 (0x284f9000) libm.so.2 => /usr/local/lib/compat/libm.so.2 (0x285d1000) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Recovering loss of /var/db/pkg ?
I'll just say it plainly: /var/db/pkg is long gone and there is no backup. It was not copied to new a machine. Is there is any hope of being able to use the ports or packages system in a meangingful way again? My sense is that some recovery is possible, but may be prohibitively expensive. Thanks for any tips! Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
recovering from a missing package database?
-- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer m...@summersault.com Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . . ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: outbound serial modem now times out or drops connection
> > Trying a new modem (US Robotics external 56k serial modem) did help > > slightly. With it, we consistently connnect, but then after a short > > pause the connection is dropped. This is easily reproduced in > > "minicom": (Using the Sprint TAP modem number here). > > > > ATDT18886561727 > > CONNECT 31200/ARQ/V34/LAPM/V42BIS > > > > NO CARRIER > > > > I'm out of ideas here. This phone line is only used for this outbound > > service, although our alarm system also uses it for outbound alerts. > > > > Any suggestions for possible causes or further troubleshooting > > approaches are appreciated. > > Does that modem support Unimodem Diagnostics? What do you get from a > '#UD' command right after the failed connection attempt? Bob, Thanks for the response! I tried that with Minicom, and the prompt just goes back to the hover over the "#" sounds and sits there. From some quick Google searches, I didn't find any mentions of this modem supporting that. I'm also not familiar with the details of the TAP protocol. After the CONNECT, who should speak next? From looking at the qpage source code, it looks like we might be waiting for "ID=" to sent from the remote end, and it is not. That would make me suspect the remote end, except that multiple remote modems are responding the same way. Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
outbound serial modem now times out or drops connection
We are using qpage to dial a remote TAP modem (Sprint and Verizon), so we can send pages about our hosting infrastructure without using the internet connection. Recently it started failing consistently with "timeout to connect". I first suspected the remote modem (Sprint), but found I got the same result with other carriers. (And Sprint denied a problem on their end). I have since tried a whole battery of approaches including having the phone line checked by the local phone company, trying a different modem and trying a different phone cord. Trying a new modem (US Robotics external 56k serial modem) did help slightly. With it, we consistently connnect, but then after a short pause the connection is dropped. This is easily reproduced in "minicom": (Using the Sprint TAP modem number here). ATDT18886561727 CONNECT 31200/ARQ/V34/LAPM/V42BIS NO CARRIER I'm out of ideas here. This phone line is only used for this outbound service, although our alarm system also uses it for outbound alerts. Any suggestions for possible causes or further troubleshooting approaches are appreciated. Thanks! Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/ums0 not initialized
> > That didn't work, I get the same error. What I have gotten to work is > using it in the PS/2 port and setting the X mouse device to /dev/psm0. > Any idea why it doesn't work with USB anymore? Do you have this set in your rc.conf file? usbd_enable="YES" Maybe you need to start or restart the usbd daemon. -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: requesting help restoring disklabel on unbootable system
On Sun, 1 Dec 2002, Mark Stosberg wrote: > On Sun, 1 Dec 2002, Mark Stosberg wrote: > > > > After an unfortunate sequence of events, my newly successfully upgraded FreeBSD 4.7 > > machine would not boot anymore and gave me a "boot:" prompt. Returning > > to the install CD disklabel program, I saw that the only partition it > > seemed be to finding was the swap partition. > > > > I recreated and wrote to disk what I thought was the old disk > > partitioning scheme (being careful not to newfs anything). After that, > > the system would boot off the drive, but would not mount /usr, /var or > > /tmp due to complains of "bad super block: magic number wrong". I > > suspect that I guessed my partition sizes wrong. > > I have a lead on solving this now. I found a tool called "find-sb" > which finds superblocks, and seemed like it could be used to make a > smarter guess about what my partition sizes should be. The trouble is, > now I'm scratching my head about how to this tool installed in a useable > state on the system since I can't boot fully in the first place. > > "find-sb": > http://gatekeeper.dec.com/pub/BSD/FreeBSD/FreeBSD-current/src/tools/tools/find-sb/ I downloaded "find-sb" and the associated Makefile, but running "make" failed with many errors on FreeBSD 4.7. I eventually addressed the issue by installing 4.7 on a new disk and restoring from backup. I still have the old disk at this point if any one has ideas how to make it functional again. -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Mail Reader Clients
On Sun, 1 Dec 2002, Philip M. Gollucci wrote: > > I'm looking for a good graphical mail reader client (to handle appx 3000 > mails per day) > I've got mail my mail working with fetchmail/procmail, so I don't need > one with filtering. Just one that > understands mbox format. Kmail and Knode (for news) seem to be really slick. I believe they are a part of the "kdenetwork" module in the KDE project. -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: /dev/ums0 not initialized
On Sun, 1 Dec 2002, Adam Bender wrote: > > When I left for break, I had a perfectly working system (FreeBSD > 4.7-CURRENT). When I came back and booted it after being down for 5 days, > when I try to start KDE I get an error saying no mouse found, device > at /dev/ums0 is not initialized. I'm using a Logitech USB mouse (I've > also tried using it with a PS/2 converter, too). Any ideas how I can > get rid of the problem and get KDE to start again? As root, try running /stand/syinstall , then select "Configure" and then "Mouse". It should help you configure and test your mouse interactively. -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: requesting help restoring disklabel on unbootable system
On Sun, 1 Dec 2002, Mark Stosberg wrote: > > After an unfortunate sequence of events, my newly successfully upgraded FreeBSD 4.7 > machine would not boot anymore and gave me a "boot:" prompt. Returning > to the install CD disklabel program, I saw that the only partition it > seemed be to finding was the swap partition. > > I recreated and wrote to disk what I thought was the old disk > partitioning scheme (being careful not to newfs anything). After that, > the system would boot off the drive, but would not mount /usr, /var or > /tmp due to complains of "bad super block: magic number wrong". I > suspect that I guessed my partition sizes wrong. I have a lead on solving this now. I found a tool called "find-sb" which finds superblocks, and seemed like it could be used to make a smarter guess about what my partition sizes should be. The trouble is, now I'm scratching my head about how to this tool installed in a useable state on the system since I can't boot fully in the first place. "find-sb": http://gatekeeper.dec.com/pub/BSD/FreeBSD/FreeBSD-current/src/tools/tools/find-sb/ -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: dump/restore after filesystem layout changes
On Sun, 1 Dec 2002, Conrad Sabatier wrote: > > Ok, now on to my question: I'd like to do a full backup on each of my > filesystems, zap all the partitions and do a new fdisk/disklabel with more > filesystems than I'm currently using. For example, create a new /home > partition instead of using a symlink in / to /usr/home. > > I'm just wondering if this will present any problems when restoring from > backups. I can't seem to glean this information from the man pages. Conrad, I did something similar once. I added a new disk that I wanted to replace my primary disk, but I wanted the partitioning a little different, like you did. It worked fine for me, copying over one partition at a time using "cpio". I imagine then it will work in your case as well. If you are interested to know about the process I used, you could browse the "disks" section on freebsddiary.org which was the basic for my methodology. -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
requesting help restoring disklabel on unbootable system
Hello, After an unfortunate sequence of events, my newly successfully upgraded FreeBSD 4.7 machine would not boot anymore and gave me a "boot:" prompt. Returning to the install CD disklabel program, I saw that the only partition it seemed be to finding was the swap partition. I recreated and wrote to disk what I thought was the old disk partitioning scheme (being careful not to newfs anything). After that, the system would boot off the drive, but would not mount /usr, /var or /tmp due to complains of "bad super block: magic number wrong". I suspect that I guess my partition sizes wrong. My questions are: Does this seem like a recoverable situation? If so, how I can restore a correct partition scheme? I have a backup of an old and valid "/etc" directory. (However, without /usr I don't seem to have enough tools to run "tar" to get at it, or use "fdformat" to create a fixit floppy at this point). Thanks! And for the curious, here's how I managed to get into this situation: After I upgraded the OS, I tried to use "sysinstall" to upgrade bash. I think the trouble was, I using bash to run sysinstall, so it failed. I then used "vipw" to upgrade the root shell to something else, but after logging out and back in, I got errors that "couldn't find /usr/local/bin/bash", so I couldn't log into the machine anymore. So then I tried installing bash from the install CD. It didn't seem to be made for this, because machine would consistently reboot in the middle of this install. At some point in debugging this problem, I may have tried to mount the drive using the installer's disklabel problem. Probabbly somewhere been that and the unexpected crashes I lost the partition map on the disk. -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
perl 5.8.0 "use.perl system" doesn't update /usr/local/bin/perl
Hello, I recently installed the Perl 5.8 port for FreeBSD easily with "make install". Thanks to the FreeBSD crew for making this so easy. It was also nice to find the "use.perl" script to easily switch between the system perl and the perl port. I ran into a small hang-up running "use.perl system" (after running "user.perl port") which I'd like to ask about. The script sucessfully updated "/usr/bin/perl", but left me with a couple oddities. First, "/usr/bin/perl5.8.0" now points to perl 5.00503, which is confusing. Secondly, "/usr/local/bin/perl" still points to the newer Perl 5.8.0. As a FreeBSD user from the 2.2.x days, I still have several perl scripts on the system that refer to "/usr/local/bin/perl", because /usr/bin/perl pointed to perl 4, if I recall correctly. It's easy enough to work around this with some symbolic links, but I expected the "use.perl system" script would have updated "/usr/local/bin/perl" to point to the older perl as well, while still preserving the perl 5.8 binary somewhere. Does anyone have any insights into why the "use.perl" script isn't taking care of this? (I'm running FreeBSD 4.5 RELEASE). -mark http://mark.stosberg.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
