I found that /bin/sh cannot handle numbers those do not fit to integer type.
That is not too bad. Too bad that it just silently warps them in arithmetical
operations:
[EMAIL PROTECTED]> /bin/sh -c 'echo $((100-1))'
2147483646
That was not a problem 5 years ago... But now we have a lot of
Aslak Evang wrote:
> howdy. I upgraded from 4.7 to 4.8 release today and have had some
> trouble afterwards.
>
> Firstly, MySQL suddenly started using huge amounts of memory, diskspace
> and cpu resulting in kernel errors
I suspect you are using the "Linux Threads" version of MySQL.
The default
Note: For really basic questions, you should probably post questions
like these to mailto:[EMAIL PROTECTED] .
-
This is the third time in 24 hours you have asked this question.
The first two times, you asked it one hour apart. The last time
you asked it on -arch, which is definitely the wrong lis
Kan Cai wrote:
> I am trying to locate the CPU interrupt handler, but with no luck. I
> guess it is somewhere in the "1386" folder, but not sure which file is
> doing the job. Could someone there shed some lights on this?
>
> Since I am trying to capture the NIC interrupts, so it should not be
Aslak,
there was a cyclic dependancy in the Xft port, cvsupping your ports should
fix this, and at the sametime fix the MySQL problem (I believe one problem
is causing the other).
Brad
> howdy. I upgraded from 4.7 to 4.8 release today and have had some
> trouble afterwards.
>
> Firstly, MySQL s
howdy. I upgraded from 4.7 to 4.8 release today and have had some
trouble afterwards.
Firstly, MySQL suddenly started using huge amounts of memory, diskspace
and cpu resulting in kernel errors
Secondly, when doing ports operations the computer starts "endless"
copies of make, until i get "Cannot
On Sat, Apr 05, 2003 at 01:01:40AM +0200, Socketd wrote:
> When updating to FreeBSD 4.8 I saw that you can give ftpd a -h flag
> when writing "syst" I still get:
> 215 UNIX Type: L8 Version: BSD-199506
You are right, there is no check. Here is the patch to fix it:
Index: ftpcmd.y
===
Hi, all:
I am trying to locate the CPU interrupt handler, but with no luck. I
guess it is somewhere in the "1386" folder, but not sure which file is
doing the job. Could someone there shed some lights on this?
Since I am trying to capture the NIC interrupts, so it should not be
exceptions. T
Hi
When updating to FreeBSD 4.8 I saw that you can give ftpd a -h flag
to prevent the server from telling clients, what kind of server it is
(finally I don't have to edit the source to uptain this "feature").
Now correct me if I am wrong, but normally you can get server
information 3 ways righ
Danny Braniss wrote:
ok, so i wrote a small script (tcl, since i don't know perl), that
does some checking, it reports for each package, the number of files
how many are realy there, and if so, checks the MD5.
now, if im not to far off, if some/all files are missing, or if the
md5 does not match,
okay...
Who knows, what's to be done and which part nobody is actually working at?
I'd like to help get it working soon, but I don't want to mess up someone
else's work.
And I need any sources of documentation on the topic - e.g. standards, if
I need any and where I can get them, etc...
On Fri,
"Matthew Emmerton" <[EMAIL PROTECTED]> writes:
> If you know that package XYZ exists in /var/db/pkg but isn't in /usr/local
> (probably because you didn't 'make deinstall' or pkg_delete it), just do
> this:
>
> rm -rf /var/db/pkg/XYZ
Umm, no, just pkg_delete it and ignore the warnings about missin
On Fri, Apr 04, 2003 at 04:14:19PM +0300, Peter Pentchev wrote:
> On Fri, Apr 04, 2003 at 02:11:58PM +0300, Danny Braniss wrote:
> >
> > > > ok, so i wrote a small script (tcl, since i don't know perl), that
> > > > does some checking, it reports for each package, the number of files
> > > > how m
On Fri, Apr 04, 2003 at 02:11:58PM +0300, Danny Braniss wrote:
>
> > > ok, so i wrote a small script (tcl, since i don't know perl), that
> > > does some checking, it reports for each package, the number of files
> > > how many are realy there, and if so, checks the MD5.
> > >
> > > now, if im not
> >
> > > > ok, so i wrote a small script (tcl, since i don't know perl), that
> > > > does some checking, it reports for each package, the number of files
> > > > how many are realy there, and if so, checks the MD5.
> > > >
> > > > now, if im not to far off, if some/all files are missing, or if th
>
> > > ok, so i wrote a small script (tcl, since i don't know perl), that
> > > does some checking, it reports for each package, the number of files
> > > how many are realy there, and if so, checks the MD5.
> > >
> > > now, if im not to far off, if some/all files are missing, or if the
> > > md5
On Thu, Apr 03, 2003 at 11:43:39PM -0800, Terry Lambert wrote:
+> IMO, it's better to use ".PATH:", which makes the problem go away,
+> by making the linker look for the objects where the compiler put
+> them (instead of making the compiler put them where the linker is
+> looking). See previous me
> > ok, so i wrote a small script (tcl, since i don't know perl), that
> > does some checking, it reports for each package, the number of files
> > how many are realy there, and if so, checks the MD5.
> >
> > now, if im not to far off, if some/all files are missing, or if the
> > md5 does not matc
On Thu, Apr 03, 2003 at 11:43:39PM -0800, Terry Lambert wrote:
[...]
> IMO, it's better to use ".PATH:", which makes the problem go away,
> by making the linker look for the objects where the compiler put
> them (instead of making the compiler put them where the linker is
> looking). See previous
19 matches
Mail list logo
