Re: /tmp getting full form portmanager
On Feb 7, 2007, at 9:32 PM, Noah wrote: From rc.conf(5): clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. Why not setup a parallel (background) task with a wrapper script to delete some files when upgrading ports? Either that or find a (more) free partition and symlink /var/tmp to it. yeah out of all the ideas this seems the easiest to implement and just makes sense but I am having difficulties creating the sym link for /tmp ns1# df -k Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s1a507630 16307630394435%/ devfs 1 1 0 100%/dev /dev/ad0s1e507630 -6467026-0%/tmp /dev/ad0s1f 150732286 7152956 131520748 5%/usr /dev/ad0s1d 2011694 129230 1721530 7%/var ns1# umount /dev/ad0s1e umount: unmount of /tmp failed: Device busy ns1# clues please? Cheers, Noah Like many things, when playing with a live filesystem your hands are pretty much tied. Booting into single user mode and remounting your / slice fixes that though ;). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
On Wednesday February 07, 2007 at 07:43:01 (PM) Noah wrote: I dont think this is an adequate solution. /tmp is filling up during the portmanager run. in other words - while I am running /tmp fills up. so it needs to be erased periodically while portmanager is running or else no other packages can be downloaded Please don't top post. If you don't know what that means, Google for it. Exactly how much space are these files taking up? I run portmanager weekly and have never, ever seen this phenomena. Yes, it does produce some temporary files to keep track of what it is doing, files to be excluded, etc., but they are relatively small. I would certainly not recommend that you delete them while portmanager is actually running though. What are you referring to by: while portmanager is running or else no other packages can be downloaded. I can log in as a different user, or simply run portmanager in the background and then proceed to download files or do virtually anything else I desire, with the possible exception of running another instance of portmanager. Exactly how are you being affected? Have you tried cleaning out the /usr/ports/distfiles directory after doing an update? Those files are not needed any more. They can take up a considerable amount of space. Perhaps you could be a little more specific about what you are attempting to do. Also, would you include the output of: df -h I would be interested in what your drive looks like. -- Gerard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
On Wed, Feb 07, 2007 at 09:32:53PM -0800, Noah wrote: From rc.conf(5): clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. Why not setup a parallel (background) task with a wrapper script to delete some files when upgrading ports? Either that or find a (more) free partition and symlink /var/tmp to it. yeah out of all the ideas this seems the easiest to implement and just makes sense but I am having difficulties creating the sym link for /tmp ns1# df -k Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s1a507630 16307630394435%/ devfs 1 1 0 100%/dev /dev/ad0s1e507630 -6467026-0%/tmp /dev/ad0s1f 150732286 7152956 131520748 5%/usr /dev/ad0s1d 2011694 129230 1721530 7%/var ns1# umount /dev/ad0s1e umount: unmount of /tmp failed: Device busy ns1# Probably several processes have something open in /tmp. Anyway, you must not be CDed to /tmp to unmount it. And if there are other processes with something open, they will have to be dealt with. Probably the easiest thing is to just go to single user and only mount root and the filesystem where you intend to put the extra large /tmp - I think you mentioned /var/tmp. Then do:/ln -s /var/tmp /tmp jerry clues please? Cheers, Noah -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
On Wed, 07 Feb 2007 21:32:53 -0800 Noah [EMAIL PROTECTED] wrote: From rc.conf(5): clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. And also daily_clean_tmps_enable (in periodic.conf) Why not setup a parallel (background) task with a wrapper script to delete some files when upgrading ports? Either that or find a (more) free partition and symlink /var/tmp to it. yeah out of all the ideas this seems the easiest to implement and just makes sense but I am having difficulties creating the sym link for /tmp That doesn't make sense to me, it just sweeps the problem under the carpet. At the moment I'm in the middle of an upgrade with portmanager, and the *total* space used on /tmp is 1MB. How much of /tmp is actually in use by portmanager. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
RW writes: clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. And also daily_clean_tmps_enable (in periodic.conf) Before doing this, understand the consequences, There's stuff in my /tmp ... I understand /who/ put it there, but not /why/. Until I affirmatively know it's safe to delete, not going to blindly reap the directory. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
On Thu, 8 Feb 2007 10:59:28 -0500 Robert Huff [EMAIL PROTECTED] wrote: RW writes: clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. And also daily_clean_tmps_enable (in periodic.conf) Before doing this, understand the consequences, There's stuff in my /tmp ... I understand /who/ put it there, but not /why/. Until I affirmatively know it's safe to delete, not going to blindly reap the directory. It's not really doing it blindly, it only removes directories and ordinary files that haven't been accessed for three days (or whatever daily_clean_tmps_days is set to). There is also a list of things to ignore. It's safer than setting clear_tmp_enable with a /tmp linked to /var/tmp, since that's the proper place for temporary files that should survive a reboot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
I sym linked /tmp to /var/tmp things are happy. thank you for everybody's help. cheers, Noah RW wrote: On Wed, 07 Feb 2007 21:32:53 -0800 Noah [EMAIL PROTECTED] wrote: From rc.conf(5): clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. And also daily_clean_tmps_enable (in periodic.conf) Why not setup a parallel (background) task with a wrapper script to delete some files when upgrading ports? Either that or find a (more) free partition and symlink /var/tmp to it. yeah out of all the ideas this seems the easiest to implement and just makes sense but I am having difficulties creating the sym link for /tmp That doesn't make sense to me, it just sweeps the problem under the carpet. At the moment I'm in the middle of an upgrade with portmanager, and the *total* space used on /tmp is 1MB. How much of /tmp is actually in use by portmanager. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
On Wednesday February 07, 2007 at 06:43:15 (PM) Noah wrote: /tmp is filling from portmanager is placing .db information and build details during its run. what options to I have to alleviate the troubles this creates? Erase them. Besides how much trouble can they be causing? Honestly, portmanager only uses those files when it runs. Each time it is restarted, except with the '--resume' flag, it erases them and creates new one. By the way, do you have: clear_tmp_enabled=YES in your /etc/rc.conf file? If not, you might want to add it if you feel that you /tmp directory is getting clogged with garbage. I believe there is a setting in periodic daily to clean out tmp files only. -- Gerard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
Hi, I dont think this is an adequate solution. /tmp is filling up during the portmanager run. in other words - while I am running /tmp fills up. so it needs to be erased periodically while portmanager is running or else no other packages can be downloaded are there other solutions? what about a sym link to /var/tmp - will that break anything? Are you sure that clear_tmp_enabled doesnt just force clearing tmp upon reboot? Cheers, Noah Gerard Seibert wrote: On Wednesday February 07, 2007 at 06:43:15 (PM) Noah wrote: /tmp is filling from portmanager is placing .db information and build details during its run. what options to I have to alleviate the troubles this creates? Erase them. Besides how much trouble can they be causing? Honestly, portmanager only uses those files when it runs. Each time it is restarted, except with the '--resume' flag, it erases them and creates new one. By the way, do you have: clear_tmp_enabled=YES in your /etc/rc.conf file? If not, you might want to add it if you feel that you /tmp directory is getting clogged with garbage. I believe there is a setting in periodic daily to clean out tmp files only. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
On Wed, Feb 07, 2007 at 03:43:15PM -0800, Noah wrote: Hi there, /tmp is filling from portmanager is placing .db information and build details during its run. what options to I have to alleviate the troubles this creates? Well, you could move /tmp to a bigger space. I think it is normally better to keep /tmp in its own partition. But, if you are running out of space and it is not reasonable to rebuild for now, then, if you have a large file system such as a /home or /scratch or whatever, make a directory there and move the /tmp stuff for now and make a symlink for it. Then, when you have the opportunity, rethink your partitioning and redo it.I tend to create my desktop with 512 MB /tmp and serious working systems sometimes with a little more. jerry Cheers, Noah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
Noah wrote: Hi, I dont think this is an adequate solution. /tmp is filling up during the portmanager run. in other words - while I am running /tmp fills up. so it needs to be erased periodically while portmanager is running or else no other packages can be downloaded are there other solutions? what about a sym link to /var/tmp - will that break anything? Are you sure that clear_tmp_enabled doesnt just force clearing tmp upon reboot? Cheers, Noah Gerard Seibert wrote: On Wednesday February 07, 2007 at 06:43:15 (PM) Noah wrote: /tmp is filling from portmanager is placing .db information and build details during its run. what options to I have to alleviate the troubles this creates? Erase them. Besides how much trouble can they be causing? Honestly, portmanager only uses those files when it runs. Each time it is restarted, except with the '--resume' flag, it erases them and creates new one. By the way, do you have: clear_tmp_enabled=YES in your /etc/rc.conf file? If not, you might want to add it if you feel that you /tmp directory is getting clogged with garbage. I believe there is a setting in periodic daily to clean out tmp files only. From rc.conf(5): clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. Why not setup a parallel (background) task with a wrapper script to delete some files when upgrading ports? Either that or find a (more) free partition and symlink /var/tmp to it. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
Jerry McAllister writes: /tmp is filling from portmanager is placing .db information and build details during its run. what options to I have to alleviate the troubles this creates? Well, you could move /tmp to a bigger space. I think the best practice would be to a) figure out why those files are left behind and b) remove them, either as part of a properly functioning portmanager session of with a separate script (perhaps from via cron). Then, when you have the opportunity, rethink your partitioning and redo it. I tend to create my desktop with 512 MB /tmp and serious working systems sometimes with a little more. May I ask what you're using /tmp for? While I could see systems which needed that, it seems a little excessive for a vanilla desktop. My FreeBSD desktop, well, see for yourself: huff@ df / Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a495726 279388 17668061%/ /tmp is 44 _k_b, and only rarely breaks 200. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp getting full form portmanager
From rc.conf(5): clear_tmp_enable (bool) Set to ``YES'' to have /tmp cleaned at startup. Why not setup a parallel (background) task with a wrapper script to delete some files when upgrading ports? Either that or find a (more) free partition and symlink /var/tmp to it. yeah out of all the ideas this seems the easiest to implement and just makes sense but I am having difficulties creating the sym link for /tmp ns1# df -k Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s1a507630 16307630394435%/ devfs 1 1 0 100%/dev /dev/ad0s1e507630 -6467026-0%/tmp /dev/ad0s1f 150732286 7152956 131520748 5%/usr /dev/ad0s1d 2011694 129230 1721530 7%/var ns1# umount /dev/ad0s1e umount: unmount of /tmp failed: Device busy ns1# clues please? Cheers, Noah -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
