Displaying 20 results from an estimated 700 matches similar to: "ICMP Error"
1999 Feb 01
5
Bind Failed on Port 139
I installed Samba 2.0.0 on a P100 running SlackWare Linux 96 (Kernel
2.0.0). After running configure, make, make install, and testparm, I
thought I was all ready to start up the smbd daemon. So I typed in
smbd -D -d 50
Got back a failure listing in the error log.
[1999/02/01 16:27:06, 0] lib/util_sock.c:open_socket_in(663
Brian Lee Bowers | Division of Government Research
Computer Aide I
2004 Oct 15
1
Building package compatible w/ R v1.9.1 and R v2.0.0?
Hi,
just in the process of updating my packages for R v2.0.0 and I have not had
time to followed the R v2.0.0 discussions so maybe my questions have already
been answered.
A concern I have is that when creating packages they should be backward
compatible with R v1.9.x for a while until all users and computers has
migrated to R v2.0.x. It is pretty straightforward to setup my packages so
that
2001 Mar 13
3
Invalid ICMP error
To anyone who is well versed with samba,
I am currently setup with ip masquerading with a cable modem connection to
my ISP. I have an error message that continues to show up on my linux box.
It says:
10.58.0.1 sent an invalid ICMP error to a broadcast.
This means it is my linux box sending an invalid packet out through my
modem. This started to happen when I installed samba. So I hav come
2004 Oct 11
2
64-bit R on Intel Xeon EM64T running fine
Dear mailing-list members,
In the days of cheap RAM and microarray applications feasting on memory,
64-bit computers become more and more useful - to actually make use of memory
beyond the magic 4GB border. I would like to report the success of running
64-bit R on an Intel Xeon EM64T machine under Linux. Just like on an AMD
Opteron, R v2.0.0 compiles fine (and out of the box) and is happily
2012 Jan 12
2
Unable to install Puppet Enterprise v2.0.0 for RHEL 5-x86_64
Hello All,
Unable to install Puppet Enterprise v2.0.0 for RHEL 5-x86_64.
[root@1801 puppet-enterprise-2.0.0-el-5-x86_64]# ./puppet-enterprise-
installer -a answers/full_suite.answer.sample
============================================================================================================================
Puppet Enterprise v2.0.0 installer
for el-5-x86_64
2014 Jul 01
2
[PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
Hi Jens and Rusty,
On Thu, Jun 26, 2014 at 8:04 PM, Ming Lei <ming.lei at canonical.com> wrote:
> On Thu, Jun 26, 2014 at 5:41 PM, Ming Lei <ming.lei at canonical.com> wrote:
>> Hi,
>>
>> These patches try to support multi virtual queues(multi-vq) in one
>> virtio-blk device, and maps each virtual queue(vq) to blk-mq's
>> hardware queue.
>>
2014 Jul 01
2
[PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
Hi Jens and Rusty,
On Thu, Jun 26, 2014 at 8:04 PM, Ming Lei <ming.lei at canonical.com> wrote:
> On Thu, Jun 26, 2014 at 5:41 PM, Ming Lei <ming.lei at canonical.com> wrote:
>> Hi,
>>
>> These patches try to support multi virtual queues(multi-vq) in one
>> virtio-blk device, and maps each virtual queue(vq) to blk-mq's
>> hardware queue.
>>
2006 Jun 04
4
eRuby & Rails: Not Compatible
I''m new to Ruby, Rails, and this list. I''ve tried searching for an
answer but it all seems to be over my head. I have all the books but
again they seem to leave me on my own to figure out the stuff that
really matters. Where is the best place to find out the details?
Exactly what are these much celebrated "naming conventions"; i.e. where
do I find an exhaustive
2006 Aug 18
4
DateBocks v2.0.0 Released
Excert from http://www.nshb.net/datebocks-2-0-0-released
Woohoo!! Finally released the next generation of DateBocks (aka
DateBox) v2.0.0.
This was a long time coming, after its initial version release allll
the way back in January, this is a nice edition to the popular tool I
released before.
This version is chalked full of features. Here is the cut out from the
CHANGELOG
== 2.0.0 - AUGUST 16,
2003 Aug 02
5
PDC Controller Error
I am trying to set up a PDC controller on a samba server, but continue
to get the following error:
The user could not be added because the following error occured:
The trust relationship between the workstation and the primary domain
failed.
An extract from the log shows only the following:
[2003/08/01 22:58:42, 0] smbd/service.c:make_connection(381)
make_connection: bkruger logged in as
2006 Jan 12
5
[Announce] Web-MeetMe v2.0.0
[New Features]
1. Added focus and tab-order to all input fields
2. Dynamic generation of date/month/year listboxes
a. It is no longer possible to schedule an invalid
date.
3. Added 'Extend' and 'End Now' buttons to the monitor
page.
4. Invite button on the monitor page. This greatly
simplifies the process of adding callers to a conference.
The ./lib/defines
2010 Jul 20
3
v2.0.rc3 released
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig
A lot of dsync fixes. I think I've fixed now all of the bugs ever
reported about dsync and I'm hopeful that it's now stable. All the rest
of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week.
Changes since rc2:
* Single-dbox is now called
2010 Jul 20
3
v2.0.rc3 released
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig
A lot of dsync fixes. I think I've fixed now all of the bugs ever
reported about dsync and I'm hopeful that it's now stable. All the rest
of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week.
Changes since rc2:
* Single-dbox is now called
2010 Mar 22
4
v2.0.beta4 released
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig
I think this release is finally feature complete. There are still some
bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1
should hopefully be out in a couple of weeks. After that v2.0.0 will be
released after no serious bugs have been found for
2010 Mar 22
4
v2.0.beta4 released
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig
I think this release is finally feature complete. There are still some
bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1
should hopefully be out in a couple of weeks. After that v2.0.0 will be
released after no serious bugs have been found for
2014 Jun 26
7
[PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
Hi,
These patches try to support multi virtual queues(multi-vq) in one
virtio-blk device, and maps each virtual queue(vq) to blk-mq's
hardware queue.
With this approach, both scalability and performance on virtio-blk
device can get improved.
For verifying the improvement, I implements virtio-blk multi-vq over
qemu's dataplane feature, and both handling host notification
from each vq and
2014 Jun 26
7
[PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
Hi,
These patches try to support multi virtual queues(multi-vq) in one
virtio-blk device, and maps each virtual queue(vq) to blk-mq's
hardware queue.
With this approach, both scalability and performance on virtio-blk
device can get improved.
For verifying the improvement, I implements virtio-blk multi-vq over
qemu's dataplane feature, and both handling host notification
from each vq and
2011 Jul 03
1
Should we use "master" for development
Hi all,
I've just pushed v2.0.0 tag to the master branch, Fedora build and ISO is in
the works and will be announced separately.
But this occasion made me thinking about our 'next' branch and I'm not sure
I like it any more: this used to be the place to do development of new
features and master was supposed to be for stable release only. This made
confusion for most of the people
2010 Aug 13
1
v2.0.rc6 released
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz.sig
I expect this to be the last release candidate. Unless release critical
bugs are reported, I'll update the version number to v2.0.0 on Monday
morning without any other changes.
Since rc5 there have been mainly some small fixes and some error message
improvements. The only
2010 Aug 13
1
v2.0.rc6 released
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz
http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz.sig
I expect this to be the last release candidate. Unless release critical
bugs are reported, I'll update the version number to v2.0.0 on Monday
morning without any other changes.
Since rc5 there have been mainly some small fixes and some error message
improvements. The only