Re: How to find files that are eating up disk space
Use df to report disk usage. Sitting in /, for example, df -sm bin will tell you the disk usage in megs in the bin directory, df -sm * will do the same for each file/dir in / man df for the whole story Cliff John Almberg wrote: Here is another newbie question that is driving me crazy, but is probably a laughable situation to an experienced admin... I've got a smallish server that is suddenly out of disk space in the '/' partition. Probably some log files have gotten out of hand. I am going to start looking for the culprits by hand... basically inspecting sub directories, but there must be a better way! Is there a command line tool that will help me figure out where the problem is? Even better, is there a way to proactively monitor the file system, so I can fix problems before I start getting 'out of disk space' errors? Any hints, much appreciated. -- John ___ 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 ___ 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: How to find files that are eating up disk space
Uh, that should be du not df :) -- Use df to report disk usage. Sitting in /, for example, df -sm bin will tell you the disk usage in megs in the bin directory, df -sm * will do the same for each file/dir in / man df for the whole story Cliff John Almberg wrote: Here is another newbie question that is driving me crazy, but is probably a laughable situation to an experienced admin... I've got a smallish server that is suddenly out of disk space in the '/' partition. Probably some log files have gotten out of hand. I am going to start looking for the culprits by hand... basically inspecting sub directories, but there must be a better way! Is there a command line tool that will help me figure out where the problem is? Even better, is there a way to proactively monitor the file system, so I can fix problems before I start getting 'out of disk space' errors? Any hints, much appreciated. -- John ___ 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 ___ 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
Compile problem with gd-2.0.28
Trying to compile gd-2.0.28 under 4.9-RELEASE. I get the error ./.libs/libgd.so: undefined reference to `pthread_mutex_unlock' ./.libs/libgd.so: undefined reference to `pthread_mutex_destroy' ./.libs/libgd.so: undefined reference to `pthread_mutex_lock' ./.libs/libgd.so: undefined reference to `pthread_mutex_init' Looks to me like a bad reference to a threads library. Any ideas ... ? Cliff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
S/KEY ftp logins
Is there some way to tell if ftp logins are successfully using S/KEY or falling back to cleartext? Is there some way to require S/KEY only? Cliff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Default /var directories/permissions in 4.9R
I've got a new 4.9R box with fbsd installed by the vendor. However, the /var partion did not get installed properly and I need to reconstruct it. I have no other 4.9 systems to compare it with and apparently it's different from the other systems we have around here. Are the default layout and permissions documented anywhere? Or could someone give me a dump of their 4.9 /var showing just the directories and their perms? Cliff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]