Displaying 20 results from an estimated 300 matches similar to: "75 seconds timeout when negotiating with smbd."
2003 May 21
1
netstat/ipcs inside jail
Hi, i've got this problem with my jail and i'm abolutly lost as in the why
of it.
I previously posted this on comp.unix.bsd.freebsd.misc but i was advised to
send here
I was unable to find help on google :(
To resume quick, when i'm in a jail, netstat doesn't work properly.
Hopefully i have provided sufficient information for anyone willing to help
me :p
First of all, my system :
2012 Nov 09
0
[LLVMdev] [NVPTX] llc -march=nvptx64 -mcpu=sm_20 generates invalid zero align for device function params
Dear all,
I'm attaching a patch that should fix the issue mentioned above. It
simply makes the same check seen in the same file for global
variables:
emitPTXAddressSpace(PTy->getAddressSpace(), O);
if (GVar->getAlignment() == 0)
O << " .align " << (int) TD->getPrefTypeAlignment(ETy);
else
O << " .align " <<
2012 Jul 11
2
[LLVMdev] [NVPTX] llc -march=nvptx64 -mcpu=sm_20 generates invalid zero align for device function params
Hello,
FYI, this is a bug http://llvm.org/bugs/show_bug.cgi?id=13324
When compiling the following code for sm_20, func params are by some reason
given with .align 0, which is invalid. Problem does not occur if compiled
for sm_10.
> cat test.ll
; ModuleID = '__kernelgen_main_module'
target datalayout = "e-p:64:64-i64:64:64-f64:64:64-n1:8:16:32:64"
target triple =
2006 Jan 26
0
Samba 3.0.21a and AIX 5.3 - Cannot see server on network
I compiled the 3.0.21a samba software with the
following configure options:
configure --prefix=/opt/samba --exec-prefix=/opt/samba
--with-krb=/usr/krb5 --with-smbwrapper --with-syslog
--with-mandir=/usr/man --with-winbind
Everything compiled fine; however, I am unable to see
the server on the microsoft network.
My smb.conf file looks like the this:
[global]
workgroup = CAREMARKRX
2003 Jul 16
1
routing to localhost
For reasons unknown, any connections to localhost -- tcp, icmp, or udp -- are
all originating from my external interface, rl0:
$ telnet localhost 25
Trying ::1...
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Can't assign requested address
telnet: Unable to connect to remote host
IPFW log:
Jul 16 12:46:43 octo ipfw: 100 Accept TCP 192.168.1.119:1434 127.0.0.1:25 out
via rl0
2003 Oct 17
1
netbios and samba
Hi all
Bear with me on this one...
We have a problem connecting to a specific port via Oracle TNSPING
There are two PC's in our office that are on the same network as the server
(i.e. my desktop PC can not get to the server)
The server has multiple network interfaces, the primary is a gigabit fibre
card on IP xx.16.
The secondary is a megabit card on IP xx.80
The tnsping command fails
2015 Jul 11
0
Problem with Samba 4.2/FreeBSD10.1
On 11/07/15 04:06, Lee Brown wrote:
> Hi Everyone, my first foray into Samba and AD both.
>
> Not sure if this is an OS or configuration problem. I've found similar
> issues, but nothing either recent enough (is related to samba 3) or close
> enough.
>
> FreeBSD-10.1-RELENG, Samba 4.2.2.
>
> I have the domain provisioned as rfc2307
> I have joined a Win7-virtual
2013 Mar 01
0
[LLVMdev] NVPTX CUDA_ERROR_NO_BINARY_FOR_GPU
Ok, as I said, the most precise way to figure out what's wrong is to emit LLVM IR first (use clang -emit-llvm ...) and check out how it differs from working examples, for instance, nvptx regression tests.
----- Original message -----
> I'm building this with llvm-c, and accessing these intrinsics via calling
> the intrinsic as if it were a function.
>
> class F_SREG<string
2013 Mar 01
0
[LLVMdev] NVPTX CUDA_ERROR_NO_BINARY_FOR_GPU
Hi Timothy,
I'm not sure what you mean by this working for other intrinsics, but
in this case, I think you want the intrinsic name
llvm.nvvm.read.ptx.sreg.tid.x.
For me, this looks like:
%x = call i32 @llvm.nvvm.read.ptx.sreg.tid.x()
Pete
On Fri, Mar 1, 2013 at 11:51 AM, Timothy Baldridge <tbaldridge at gmail.com> wrote:
> I'm building this with llvm-c, and accessing these
2015 Jul 11
1
Problem with Samba 4.2/FreeBSD10.1
On 11/07/15 10:16, Rowland Penny wrote:
> On 11/07/15 04:06, Lee Brown wrote:
>> Hi Everyone, my first foray into Samba and AD both.
>>
>> Not sure if this is an OS or configuration problem. I've found similar
>> issues, but nothing either recent enough (is related to samba 3) or
>> close
>> enough.
>>
>> FreeBSD-10.1-RELENG, Samba 4.2.2.
2004 Nov 08
0
3.0.7 server "NetBIOS over TCP disabled -- no workgroup available"
win2k/XP clients can access this fine, but not NT clients.
Samba is listening on the netbios-dgm/ns ports and there's no packet
filtering:
udp4 0 0 atarashii.netbios-dgm *.*
udp4 0 0 atarashii.netbios-ns *.*
udp4 0 0 *.netbios-dgm *.*
udp4 0 0 *.netbios-ns *.*
2008 Apr 23
0
Running Samba 3 in a FreeBSD jail
Hello,
I've been trying to get a solution (or at least an explanation) from the FreeBSD guys
at freebsd-questions lists, but I guess no one knew the answer.
I am trying to run Samba 3 (latest) in a FreeBSD 7.0 jail
(http://en.wikipedia.org/wiki/FreeBSD_Jail). It seems I cannot convince Samba to answer
NetBIOS broadcast requests and therefore Windows machines cannot browse it directly
by name
2015 Jul 11
2
Problem with Samba 4.2/FreeBSD10.1
Hi Everyone, my first foray into Samba and AD both.
Not sure if this is an OS or configuration problem. I've found similar
issues, but nothing either recent enough (is related to samba 3) or close
enough.
FreeBSD-10.1-RELENG, Samba 4.2.2.
I have the domain provisioned as rfc2307
I have joined a Win7-virtual machine to the domain
I have created a new user with ADUC
I have assigned 10000 to
2013 Mar 01
1
[LLVMdev] NVPTX CUDA_ERROR_NO_BINARY_FOR_GPU
The identifier INT_PTX_SREG_TID_X is the name of an instruction as the
back-end sees it, and has very little to do with the name you should use in
your IR. Your best bet is to look at the include/llvm/IR/IntrinsicsNVVM.td
file and see the definitions for each intrinsic. Then, the name mapping is
just:
int_foo_bar -> llvm.foo.bar()
int_ prefix becomes llvm., and all underscores turn into
2004 Jan 18
7
arp problem in /var/log/messages
hi all, i got flooded by these msgs like 1000+ lines, any idea?
my kernel is dated Nov-30 FreeBSD 4.9-stable
# tail -f /var/log/messages
Jan 18 19:43:23 xb /kernel: arp: 202.79.180.1 moved from 00:04:5a:49:eb:74
to 00:50:0f:4f:c0:00 on rl0
Jan 18 19:45:06 xb /kernel: arp: 202.79.180.1 moved from 00:50:0f:4f:c0:00
to 00:04:5a:49:eb:74 on rl0
Jan 18 19:45:18 xb /kernel: arp: 202.79.180.1 moved from
2003 Jul 17
1
device troubles after stable update
After updating my kernel from a 4.7-stable to 4.8-stable update, my SB PCI128 is no longer recognized by the pcm driver.
Here is my dmesg:
FreeBSD 4.8-STABLE #0: Thu Jul 17 14:13:52 CDT 2003
root@hautlos.stout.osu-res.okstate.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU)
Origin =
2017 Feb 07
0
ntp and samba43 on FreeBSD-103.
On Tue, 2017-02-07 at 13:06 -0500, James B. Byrne via samba wrote:
> Recently we have been having a lot of trouble with time
> synchronisation between our samba DC and the domain clients. We are
> not sure what started this issue since the Samba domain went live on
> October 11, 2016 and the issues only began to surface this past
> January but at some point the time on the clients
2017 Feb 08
0
ntp and samba43 on FreeBSD-103.
On Tue, February 7, 2017 13:06, James B. Byrne wrote:
> In any case, we have resolved most of these issues. In dealing with
> this I ran across
> https://wiki.samba.org/index.php/Time_Synchronisation which contains
> this instruction:
>
> Set up the ntpd.conf File on a DC
> . . .
> ntpsigndsocket /usr/local/samba/var/lib/ntp_signd/
>
> Now, on the FreeBSD host I
2007 Mar 01
1
GLM problems.
Dear R users I'm new in R management and maybe It's a silly question. I'm
working with GLM to obtain predictive models. I have some problesm with the
prediction instruction:
> DatosTotal <- read.csv("Var_perdizcsv.csv", sep =";")
> edvariable <- edit(DatosTotal)
> pre <- predict(rlfinal, DatosTotal, type = 'probs')
Erro en
2017 Feb 07
5
ntp and samba43 on FreeBSD-103.
Recently we have been having a lot of trouble with time
synchronisation between our samba DC and the domain clients. We are
not sure what started this issue since the Samba domain went live on
October 11, 2016 and the issues only began to surface this past
January but at some point the time on the clients and the DC diverged
enough that we began to get strange network errors. Once we figured
out