Displaying 20 results from an estimated 80 matches similar to: "smbd -F: standard input is not a socket, assuming -D option"
2012 Jul 20
0
RuntimeError: Unable to find partition containing kernel
Hardware:
2x Intel Xeon Quad-Core 2.33GHz
24GB FBDIMM RAM
2x 2TB HDD in RAID-1
Intel Server Board S5400SF
Setup:
Arch Linux x86_64
Xen 4.1.2
Grub2 Multiboot
Synopsis:
I set up a new VM for Debian Squeeze following instructions here:
http://www.howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0.
Partitioning & installation completed correctly. When I tried to run the
2003 Jun 01
1
Very weird network behaviour with 4.7-RELEASE-p10 (large)
Hi,
I have been doing some tests using hping2 and TCP SYN
pings targeting local and remote hosts from two FreeBSD
4.7-RELEASE-p10 and one Linux 2.4.18 host.
The three machines have the same hardware configuration
and have been running for 6 months now. The average load
isnt too high (usually 0.01 to 0.15) on the FreeBSD machines.
Here is the output from hping2 (excuse me the line wrap),
2019 Aug 07
2
Bind9 doesn't updated - TSIG error with server: tsig verify failure
Hello everybody,
I've had a samba environment with the following "brief" description:
- There are 2 DC (*samba4 *and *samba4bkp*) running samba version 4.1.6
on my domain (*SMB*). DNS back end is Samba Internal DNS;
- I've added a new DC (*king*) running samba version 4.10.2 and as DC
to *SMB *domain with BIND9 DNS Back End;
- *king* has updated dns zones and
2017 Aug 07
1
gluster stuck when trying to list a successful mount
Hi all,
My infrastructure is GlusterFS with 2 Nodes:
L137B-GlusterFS-Node1.L137B-root.com
L137B-GlusterFS-Node2.L137B-root.com
I have followed this guide:
http://www.itzgeek.com/how-tos/linux/centos-how-tos/install-and-configure-glusterfs-on-centos-7-rhel-7.html/2
I have created a device, formatted as ext4, mounted it.
The next step was to install gluster FS.
I installed glusterfs 3.10.3,
2013 Jan 11
0
Samba 4 TSIG Error "NOTIMP"
Hi!
I've got troubles with dynamic dns updates.
Ubuntu: 12.04 / Samba 4.0.0 / followed off. howto
Winsrv: Server 2k8R2
root at tuxsrv:/home/schau# samba -V
Version 4.1.0pre1-GIT-94f11e9
root at tuxsrv:/home/schau# kinit administrator at SCHAU.LOCAL
Password for administrator at SCHAU.LOCAL:
root at tuxsrv:/home/schau# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: administrator
2002 Feb 18
1
Unknown DOS version
Hello,
what does the wine error message "unknown DOS version" mean? Will I have
to change my wine configuration in some way? Or is the program not
runnable with wine at all?
Any hints are appreciated. Thanks in advance.
Martin
2014 Mar 17
2
[LLVMdev] GSOC - Use more StringRef in clang.
Hello,
I was looking to tackle the "StringRef'ize APIs" suggestion from the
clang project page and just wanted to post a couple of thoughts and ask
a couple of questions.
First of all I am going to talk about how I see the goals of the
project. Basically, as far as I understand it I will be converting
existing functions that take std::string or char*'s to use
llvm::StringRef
2007 Sep 18
0
Bug#443024: xen-3: FTBFS: xc_core.c:195: warning: assuming signed overflow does not occur when assuming that (X + c) < X is always false
Package: xen-3
version: 3.1.0-2
Severity: serious
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20070917 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
make[5]: Entering directory `/build/user/xen-3-3.1.0/debian/build/build-utils_i386/tools/libxc'
gcc -O2 -fomit-frame-pointer -m32 -march=i686
2006 Dec 02
0
Assuming write caching from CentOS 4.4 to iSCSI device
Hi list,
CentOS 4.4 connecting to Promise M500i iSCSI disk array. 2/4 servers
connect fine with iscsi-initiator-utils-4.0.3.0-4. The other 2 servers
have this in dmesg:
SCSI device sdb: 1 512-byte hdwr sectors (0 MB)
sdb: asking for cache data failed
sdb: assuming drive cache: write through
SCSI device sdb: 1 512-byte hdwr sectors (0 MB)
sdb: asking for cache data failed
sdb: assuming drive
2009 Feb 16
4
assuming AR(1) residuals in OLS
Hi to all,
In other statistical software, such as Eviews, it is possible to
regress a model with the Least Squares method, assuming that the
residuals follow an AR(q) process.
For example the resulting regression is something like
y = 1.2154 + 0.2215 x + 0.251 AR(1)
How is it possible to do the same in R?
Thank you very much in advance,
Constantine Tsardounis
http://www.costis.name
2014 Dec 15
0
Re: index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow]
On Mon, Dec 15, 2014 at 05:54:51PM +0000, Richard W.M. Jones wrote:
> No idea why this happens:
>
> index-parse.y: In function 'yyparse':
> index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow]
> if (yyss + yystacksize - 1 <= yyssp)
> ^
>
> It only happens on one machine,
2004 Jul 23
0
R: R: retrieve rows from frame assuming criterion [corrected]
Yes,
paraphrasing Murphy I can say of myself:
"Nothing seems to be able to stop a stupid thought
in its pathway from the brain to the keyboard". :-)
Sorry once again and thank for your patience.
Stefano
> -----Messaggio originale-----
> Da: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk]
> Inviato: venerd?? 23 luglio 2004 16.30
> A: Guazzetti Stefano
> Cc: Luis
2004 Jul 23
0
retrieve rows from frame assuming criterion [corrected]
Still wrong:
> x <- data.frame(a = sample(letters[1:3], 10, replace=T), b=1:10)
> x
a b
1 a 1
2 a 2
3 b 3
4 b 4
5 a 5
6 a 6
7 b 7
8 b 8
9 b 9
10 c 10
> subset(x, a == c("b", "c"))
a b
3 b 3
7 b 7
9 b 9
10 c 10
> subset(x, a %in% c("b", "c"))
a b
3 b 3
4 b 4
7 b 7
8 b 8
9 b 9
10 c 10
What matters
2004 Jul 23
1
R: retrieve rows from frame assuming criterion [corrected]
sorry for my previus (WRONG)
answer, as someone already pointed out
a solution could be
subset(data, PUNTAR==c("IX49","IX48"))
> -----Messaggio originale-----
> Da: Guazzetti Stefano
> Inviato: venerd?? 23 luglio 2004 15.55
> A: 'Luis Rideau Cruz'; r-help at stat.math.ethz.ch
> Oggetto: R: [R] retrieve rows from frame assuming criterion
>
>
2014 Dec 15
2
index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow]
No idea why this happens:
index-parse.y: In function 'yyparse':
index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow]
if (yyss + yystacksize - 1 <= yyssp)
^
It only happens on one machine, and not on any others, even
though they have similar versions of gcc and bison installed.
Rich.
--
Richard
2004 Jul 23
2
retrieve rows from frame assuming criterion
Hi all,
I have a data frame in which one column(PUNTAR) is of character type.
What I want is to retrieve is the frame but only with those rows matching elements of PUNTAR with a list characters (e.g c("IX49","IX48") )
Year TUR STODNR PUNTAR
1994 9412 94020061 IX49
1994 9412 94020062 IX48
1994 9412 94020063 X32
1994 9412 94020065 X23
1994 9412
2019 May 03
2
RFC: On removing magic numbers assuming 8-bit bytes
Jeroen Dobbelaere via llvm-dev <llvm-dev at lists.llvm.org> writes:
> Hi Jesper,
>
>> Thanks, these are interesting differences. The CHAR_BIT and byte
>> relation is established in the C standard and I would prefer the byte
>> terminology. It means the same thing as addressable unit but is a bit
>> shorter and probably more widely known.
>
> Looking
2019 May 06
2
RFC: On removing magic numbers assuming 8-bit bytes
I agree, addressable unit size is probably a better abstraction.
However, in the lib/CodeGen directory alone, there's some 785 uses of
the word "byte" and a significant fraction of the code that we want to
modify is using the byte terminology today. An example of unmodified
code from my showcase patch set:
assert(!(Shift & 0x7) == 0 &&
"Shifts not
2019 May 02
2
RFC: On removing magic numbers assuming 8-bit bytes
> -----Original Message-----
> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of JF
> Bastien via llvm-dev
>
> I’m not a fan of C and C++ supporting anything but 8 bits per byte.
> Realistically, C and C++ on such targets are different languages from 8-
> bit-per-byte C and C++, and therefore code isn’t portable from one to the
> other.
Having done
2019 May 03
2
RFC: On removing magic numbers assuming 8-bit bytes
Hi Jeroen,
Thanks, these are interesting differences. The CHAR_BIT and byte
relation is established in the C standard and I would prefer the byte
terminology. It means the same thing as addressable unit but is a bit
shorter and probably more widely known.
Do you suggest any in-tree changes at some call sites using the
suggested AdressSpace parameter or would we rely on the default value
always?