>>> On Sun, 27 Aug 2006 05:35:22 +0200 (CEST),
>>> Dirk Engling <[EMAIL PROTECTED]> wrote:
erdgeist> Still: FreeBSD's /etc/ assumes and provides a working mail subsystem
in
erdgeist> its default configuration. That exposes sendmail to the publicly
visible
erdgeist> IP address. Shutting the mai
Peter Jeremy wrote:
On Thu, 2006-Aug-24 17:39:56 +0200, Daniel A. wrote:
My server crashes very often and it's very random.
...
panic: machine check trap
...
As far as I understand, the issue is CPU-related, but that doesn't make
sense, as my network interface cards are constantly giving me
On Sat, Aug 26, 2006 at 08:19:40PM -0500, Eric Anderson wrote:
> On 08/26/06 07:44, Pawel Jakub Dawidek wrote:
> >On Sat, Aug 26, 2006 at 07:23:36AM -0500, Eric Anderson wrote:
> >>Hmm - had another panic. Again, screen shots are here:
> >>
> >>http://www.googlebit.com/freebsd/snapshots/gjournal_p
I have the following problem: since I need and do not like any
kind of
smtp activity in my jails (there's no 127.0.0.1 in a jail, all
services
[...]
cron tries to deliver its status mails and fails.
try 'MAILTO=""' in /etc/crontab
That will work for any custom Cron just that you've set, bu
> The default configuration doesn't expose sendmail to the publicly
> visible IP addres. The daemon it runs only listens for connections to
> the localhost address.
Unfortunately, in jails, localhost gets remapped to the jail IP
address and therefore, he is correct, it is accepting connections
fro
In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
> On Sat, Aug 26, 2006 at 03:43:26PM -0400, Mike Meyer wrote:
> >>> Hmm. My copy of the port sets that for amd64 already. Checking the CVS
> >>> repository, it looks like a number of things have broken/unbroken in
> >>> the last few day
In <[EMAIL PROTECTED]>, Dirk Engling <[EMAIL PROTECTED]> typed:
> On Sat, 26 Aug 2006, Mike Meyer wrote:
> > Except some of the things run from cron want to send mail all on their
> > own, so fixing cron won't solve your problem.
> > Why are you running cron inside the jails at all? Are you letting
On Sat, 26 Aug 2006, Mike Meyer wrote:
Except some of the things run from cron want to send mail all on their
own, so fixing cron won't solve your problem.
Why are you running cron inside the jails at all? Are you letting your
users run it? If not, can you disable it, and instead run scripts f
In <[EMAIL PROTECTED]>, Dirk Engling <[EMAIL PROTECTED]> typed:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> I have the following problem: since I need and do not like any kind of
> smtp activity in my jails (there's no 127.0.0.1 in a jail, all services
> listen to the jails e
> I have the following problem: since I need and do not like any kind of
> smtp activity in my jails (there's no 127.0.0.1 in a jail, all services
[...]
> cron tries to deliver its status mails and fails.
try 'MAILTO=""' in /etc/crontab
[SorAlx] ridin' VN1500-B2
On 08/26/06 07:44, Pawel Jakub Dawidek wrote:
On Sat, Aug 26, 2006 at 07:23:36AM -0500, Eric Anderson wrote:
Hmm - had another panic. Again, screen shots are here:
http://www.googlebit.com/freebsd/snapshots/gjournal_panic2/
I can't find panic message. What was it?
It was a deadlock.
Er
Hello Dirk,
Sunday, August 27, 2006, 2:13:03 AM, you wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> Hello,
> I have the following problem: since I need and do not like any kind of
> smtp activity in my jails (there's no 127.0.0.1 in a jail, all services
> listen to the jails externa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have the following problem: since I need and do not like any kind of
smtp activity in my jails (there's no 127.0.0.1 in a jail, all services
listen to the jails external interface), I put those lines into my
/etc/rc.conf:
sendmail_enable="NO
In <[EMAIL PROTECTED]>, Peter Jeremy <[EMAIL PROTECTED]> typed:
> >> > > > 3) openoffice doesn't build on amd64, and the i386 build doesn't run
> >> > > >on amd64, so the recommended way to run openoffice on amd64 is to
> >> > > >run the Linux build.
> OOo2.0 should (and generally does) bui
In <[EMAIL PROTECTED]>, Mario Lobo <[EMAIL PROTECTED]> typed:
> Hi;
>
> My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
> 'work' directories !
>
> Removing them one by one was a pain so I wrote this little utility to wipe
> them off.
Setting WORDIRPREFIX in /etc/ma
albi:
On Sun, 27 Aug 2006 03:12:52 +0400
Roman Kurakin <[EMAIL PROTECTED]> wrote:
Rick C. Petty:
On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
My /usr/ports directory was occuping 24 gigs, of which 20 was
just from the 'work' directories !
Removing them one b
On Sun, Aug 27, 2006 at 01:13:19AM +0200, albi wrote:
>
> > > I find that the following command works just fine for me:
> > >
> > > find /usr/ports -type d -name work -prune -print -delete
> > >
> > A bit rude, but also works
> >
> > cd /usr/ports && make clean
>
> guys... please use the offi
* albi <[EMAIL PROTECTED]> [2006-08-27 01:13 +0200]:
> guys... please use the official portsclean ! :)
>
> included in the sysutils/portupgrade
>
> portsclean -h
> portsclean 2.0.1 (2006/06/13)
>
> usage: portsclean [-hCDDiLnPPQQq]
>
> -h, --help Show this message
> -C, --workc
On Sat, Aug 26, 2006 at 03:43:26PM -0400, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
>> On Sat, Aug 26, 2006 at 02:40:24PM -0400, Mike Meyer wrote:
>>> I'm not sure what you're saying is false - that the compiler can
>>> generate i386 binaries, or that the re
On Sun, 27 Aug 2006 03:12:52 +0400
Roman Kurakin <[EMAIL PROTECTED]> wrote:
> Rick C. Petty:
> > On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
> >
> >> My /usr/ports directory was occuping 24 gigs, of which 20 was
> >> just from the 'work' directories !
> >>
> >> Removing them on
> I find that the following command works just fine for me:
>
> > find /usr/ports -type d -name work -prune -print -delete
>
> And EVEN cooler is having a
>
> WRKDIRPREFIX= /var/ports
>
> in your /etc/make.conf, that way an "rm -rf /var/ports/*" cleans without
> unnecessary directory recu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roman Kurakin wrote:
> A bit rude, but also works
>
> cd /usr/ports && make clean
This one takes ages, every port is being cleaned which in turn cleans
every dependency, so low level ports will be "make clean"ed thousand
times. Better would be
for
On Sat, 2006-Aug-26 15:43:26 -0400, Mike Meyer wrote:
>In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
>> On Sat, Aug 26, 2006 at 02:40:24PM -0400, Mike Meyer wrote:
>> > In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
>> > > On Sat, Aug 26, 2006 at 02:00:51PM -0400, M
Rick C. Petty:
On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
'work' directories !
Removing them one by one was a pain so I wrote this little utility to wipe
them off.
I find that the following
On Saturday 26 August 2006 20:01, you wrote:
> Actually, it is a big deal for some people. Why the GPL?
> You are posting to a FreeBSD list.
You're right, but I build it in kdevelop and it put it there so I felt I
should leave it there.
--
Mario Lobo
http://www.mallavoodoo.com.br
99% rwindows F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick C. Petty wrote:
> On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
>> My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
>> 'work' directories !
>>
>> Removing them one by one was a pain so I wrote this little
Hello Mario,
Sunday, August 27, 2006, 12:19:06 AM, you wrote:
> Hi;
> My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
> 'work' directories !
> Removing them one by one was a pain so I wrote this little utility to wipe
> them off.
try portsclean(1) which IIRC belong
Daniel A. wrote:
Hi guys,
My server crashes very often and it's very random. So not long ago, I
was suggested that I read the FreeBSD Handbook pages about kernel
debugging, and here is the result:
[EMAIL PROTECTED] DIENUB $ kgdb kernel.debug /var/crash/vmcore.3
[GDB will not be able to debug u
On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
>
> If you find it useful, pass it on. Its not a big deal but thanks for keeping
> the credits on it.
Actually, it is a big deal for some people. Why the GPL?
You are posting to a FreeBSD list.
--
Steve
__
On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote:
>
> My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
> 'work' directories !
>
> Removing them one by one was a pain so I wrote this little utility to wipe
> them off.
I find that the following command works
Hi;
My /usr/ports directory was occuping 24 gigs, of which 20 was just from the
'work' directories !
Removing them one by one was a pain so I wrote this little utility to wipe
them off.
If you find it useful, pass it on. Its not a big deal but thanks for keeping
the credits on it.
Last but
In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
> On Sat, Aug 26, 2006 at 02:40:24PM -0400, Mike Meyer wrote:
> > In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
> > > On Sat, Aug 26, 2006 at 02:00:51PM -0400, Mike Meyer wrote:
> > > > 1) The compiler can build i386 bi
On Sat, Aug 26, 2006 at 02:40:24PM -0400, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
> > On Sat, Aug 26, 2006 at 02:00:51PM -0400, Mike Meyer wrote:
> > > 1) The compiler can build i386 binaries, but the toolchain in general
> > >doesn't do the right thin
In <[EMAIL PROTECTED]>, Steve Kargl <[EMAIL PROTECTED]> typed:
> On Sat, Aug 26, 2006 at 02:00:51PM -0400, Mike Meyer wrote:
> > 1) The compiler can build i386 binaries, but the toolchain in general
> >doesn't do the right thing with the -m32 flag.
> I believe that this may be false because the
On Sat, Aug 26, 2006 at 02:00:51PM -0400, Mike Meyer wrote:
>
> 1) The compiler can build i386 binaries, but the toolchain in general
>doesn't do the right thing with the -m32 flag.
I believe that this may be false because the compiler is
not built with multilib enabled.
> 2) The system can
metaquestions:
The amd64 ilst might be a better place for this, but it's listed as
"for discussion of porting FreeBSD to amd64", and these aren't really
questions about porting FreeBSD to amd64. Maybe the list needs to be
repurposed?
There doesn't appear to be a FAQ (or FAQ section) for
platform-
The periodic.conf in 7-CURRENT is still set to use the INDEX-6 ports
index file, instead of INDEX-7 which is the default on 7-CURRENT. This
should, I think, be changed.
I apologize if I've posted to the wrong mailing list.
Patch to change /etc/defaults/periodic.conf attached.
Regards!
//Nicla
On Sat, Aug 26, 2006 at 07:23:36AM -0500, Eric Anderson wrote:
> Hmm - had another panic. Again, screen shots are here:
>
> http://www.googlebit.com/freebsd/snapshots/gjournal_panic2/
I can't find panic message. What was it?
--
Pawel Jakub Dawidek http://www.wheel.pl
[EMA
On 08/24/06 23:13, Eric Anderson wrote:
On 08/24/06 05:54, Pawel Jakub Dawidek wrote:
On Tue, Aug 22, 2006 at 03:38:15PM -0500, Eric Anderson wrote:
Did you get a chance to look at those screenshots? I'm curious to know if you also think it is gjournal related. I've stopped loading gjournal, a
On Sun, 20 Aug 2006 17:24:35 +0900
Norikatsu Shigemura <[EMAIL PROTECTED]> wrote:
> 1. assume only 1 CPU.
> 2. assume dev.cpu.0.freq is always exists.
> 3. display position is good?
I modified 1 and 2. Please check attached diff.
I couldn't fix 3 issue. So I ass
On Fri, Aug 25, 2006 at 09:22:26PM -0500, Eric Anderson wrote:
> I got this error today, while some very heavy disk access was occurring:
>
>
> Aug 25 13:47:07 snapshot1 kernel: fsync: giving up on dirty
> Aug 25 13:47:07 snapshot1 kernel: 0xff01bbb99a20: tag devfs, type VCHR
> Aug 25 13:47:0
41 matches
Mail list logo
