On Fri, 22 May 2009, Steve Bertrand wrote:
Luke Dean wrote:
I ended up rebooting the box.
Was there any other possible solution I could've tried?
You have to restart the service that was holding the log file(s) open.
The system does not release the space while an application is 'using'
the
On Friday 22 May 2009 18:19:25 Steve Bertrand wrote:
> # pkg_add -r lsof
Or use the native fstat(1).
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "fre
On Fri, May 22, 2009 at 9:14 AM, Luke Dean wrote:
>
> Yes, it sounds like a stupid question, but let me tell the story.
>
> The log for my dhcp server filled up /var last night, which meant that
> dhcpd was also unable to hand out new leases, which meant that I had
> effectively been DOSed. I'll
Luke Dean writes:
> Yes, it sounds like a stupid question, but let me tell the story.
>
> The log for my dhcp server filled up /var last night, which meant that
> dhcpd was also unable to hand out new leases, which meant that I had
> effectively been DOSed. I'll have to look into changing my log
Luke Dean wrote:
>
> Yes, it sounds like a stupid question, but let me tell the story.
>
> The log for my dhcp server filled up /var last night, which meant that
> dhcpd was also unable to hand out new leases, which meant that I had
> effectively been DOSed. I'll have to look into changing my lo
Yes, it sounds like a stupid question, but let me tell the story.
The log for my dhcp server filled up /var last night, which meant that
dhcpd was also unable to hand out new leases, which meant that I had
effectively been DOSed. I'll have to look into changing my logging
policies.
So, to corr
