Displaying 20 results from an estimated 1000 matches similar to: "smbd core-dumping when removing file; mis-configuration?"
2015 Feb 05
0
Another Fedora decision
On Wed, February 4, 2015 17:16, Lamar Owen wrote:.
>
> Now, I have seen this happen, on a system in the wild, where the very
> first thing the attacker did was grab a copy of /etc/shadow, even with
> an interactive reverse shell and root access being had. So even when
> you recover your system from the compromise you have the risk of all
> those passwords being known, and
2023 Oct 13
1
rnrfa package problems
R help email
Hello I?m trying to work my way through the rnrfa package
RJ-2016-036.pdf (r-project.org)
<https://journal.r-project.org/archive/2016/RJ-2016-036/RJ-2016-036.pdf>
I?ve got it loaded OK and can access the data by the catalogue() command -
gives me a tibble with names, grid refs etc
allStations <- catalogue()
allStations
This works OK
But when I try to run the example
2015 Apr 22
0
CentOS-6.6 - wget $? returns 0 when invalid protocol used
Can someone enlighten me why this:
wget --quiet --no-check-certificate
ttps://flub.githubusercontent.com/jodrell/jwhois/master/example/jwhois.conf
; echo $?
returns this:
0
When wget --no-quiet says this:
wget --no-quiet --no-check-certificate
ttps://flub.githubusercontent.com/jodrell/jwhois/master/example/jwhois.conf
; echo $?
2017 Jun 06
2
bind update flubbed somehow?
hey folks, we upgraded bind last night to bind-9.8.2-0.62.rc1.el6_9.1.x86_64
and now our server seems to not be able to update. Whenever we add
records and update the soa and reload,
it still shows the old data..
so for example, we have
[root at bind1 /var/named]$grep servername domainname.net.zone
[root at bind1 /var/named]$nslookup -port=5353 servername 10.115.76.87
Server: 10.10.76.87
2017 Jun 06
0
bind update flubbed somehow?
--On Tuesday, June 06, 2017 10:53 AM -0400 Jason Welsh
<jason.welsh at mercurygate.com> wrote:
> [root at bind1 /var/named]$nslookup -port=5353 servername 10.115.76.87
nslookup is deprecated. What does dig say? It's much more informative and
shows all the details of the query and reply packets.
---
This email has been checked for viruses by Avast antivirus software.
2017 Jun 06
1
bind update flubbed somehow? (resolved)
ugh, the upgrade changed the owner from named to root on /var/named
where my zone files are and
therefore named could not read the zone files.. How embarrassing.. ;)
Jason
On 06/06/2017 09:58 AM, Kenneth Porter wrote:
> --On Tuesday, June 06, 2017 10:53 AM -0400 Jason Welsh
> <jason.welsh at mercurygate.com> wrote:
>
>> [root at bind1 /var/named]$nslookup -port=5353
2009 May 25
1
Vista authorization issues (PR#13718)
Full_Name: David Kesling
Version: 2.9.0
OS: Windows Vista & XP sp2
Submission from: (NULL) (65.166.169.237)
I upgraded to 2.9.0 on my desktop (XP) and my laptop (Vista Home Basic). The XP
machine (with both Tinn-R and JGR) is running just fine... very happy. The
laptop is NOT doing too well. I've had to activate the XP-compatability mode AND
run Rgui as administrator... and there still
2014 Feb 12
0
locking smbd
dear all,
i'm running samba4 (4.0.x) on FreeBSD 9.2 and stuck at leas once a week with the following smbd fault (taken fom /var/log/messages):
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.344706, ?0, pid=5960, effective(3000028, 20), real(0, 0)] ../lib/util/fault.c:72(fault_report)
Feb 12 10:37:56 mercury smbd[5960]: ?
2014 Mar 24
1
samba4.0.16 smbd internal error
Dear list,
I keep getting strange "internal error"s from smbd. I increased the log level to 3 and pasted the relevant log snippet. Does anyone know (or guess) what's going on? What should I check? Any direction to investigate?
Thanks a lot,
Sascha
? ===============================================================
[2014/03/24 13:28:49.787910, ?0, pid=13041, effective(3000026, 20),
2005 May 16
1
Problem (mis-configuration?) with Milter-Sender (v0.62) GreyListRejectCount...
Hi, I''m having a problem with Milter-Sender (v0.62) in the fact that I''m not able to tune the GreyListRejectCount the way that I want to. Namely I''m having a problem setting the GreyListRejectCount to any value higher than a single digit, or at least that''s what I think is happening. I''ve been ""fighting this problem for a while on my server
2003 Nov 24
1
ia64 mis-merge
Peter,
There was a mis-merge in the ia64 patch you put into 0.83. Olaf Hering
pointed it out. The patch is attached. Olaf claims that he is still
unable to compile for ia64 with is toolchain. He's getting the
following error:
<olh> libc.so(.got+0x0): multiple definition of `_GLOBAL_OFFSET_TABLE_'
<olh> tests/getenvtest.o(.got.plt+0x0): first defined here
<olh>
2010 Feb 28
0
[LLVMdev] C infinite recursion mis-optimized?
Hi Isaac,
> For fun, I made a recursive function, but LLVM optimized it wrong (if
> I'm understanding C standards correctly).
>
> "void f() { f(); }"[see llvm-code in footnote 1]
> was optimized to be equivalent to "void f() {}"[also 1]. I believe it
> should either be equivalent in effect to "void f() { while(1){} }"[2],
> which produces an
2010 Feb 28
1
[LLVMdev] C infinite recursion mis-optimized?
On 02/28/10 07:39, Duncan Sands wrote:
> Hi Isaac,
>
>> For fun, I made a recursive function, but LLVM optimized it wrong (if
>> I'm understanding C standards correctly).
>>
>> "void f() { f(); }"[see llvm-code in footnote 1]
>> was optimized to be equivalent to "void f() {}"[also 1]. I believe it
>> should either be equivalent in
2009 May 12
2
Today's git mis-reads CTL-S
When running Notepad2 with today's git wine, the keystrokes CTL-S no longer works. Instead, it displays CTL-S on the page in a funny little black box.
I have Karmic Koala and the new 2.6.20 kernel, 'tis true, but CTL-S worked this morning.
??
Susan
wine-1.1.21-62-gb045342
2018 Nov 01
0
SAY command (mis)behaviour?
>
> I boot my system with the attached extlinux.conf, which has some
> entries to boot old kernels. When i'm booting the old versions i'd
> like to have a reminder message recalling me that the most recent
> kernel is not being used, so that i don't forget to switch back to it,
> for example after many days of uptime.
>
> Now, is it normal that _every_ SAY
2018 Nov 01
0
SAY command (mis)behaviour?
> Thank you for your fast and in-depth reply, and for the practical
> example. I think i will dig deeper into the modules part of the wiki,
> which i skipped when i first configured the bootloader some time
> ago...
One of the "over-complicated" ways to circumvent the limitation (i.e.
SAY being a global directive, not a per-label directive) without using
modules would be
2007 Aug 02
2
MD5 mis-match
Hi all,
I'm almost finished building our new load balanced email server that are
attached to an NFS mountpoint. There are currently two e-mail servers
connected to the NFS share. Both email servers are running CentOS 4.5 with
Postfix 2.4.3, Dovecot 0.99, and authenticating via LDAP.
Dovecot is using Maildir format. I've been trying to do some benchmarks
using Postal and Rabid, and
2013 May 03
1
CATENATE mis-reads literal after bad URL
Dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes mishandles literals after bad URLs. (As before remember that the "foobar" text below is really "foobarCRLF" hence the length of 8. Also, last time some MTA discarded an important single leading space character in the snippet I quoted so this time I'm prefixing all the lines to avoid that. In case it's
2007 Apr 26
0
winbindd PID name resolution mis-behaviour with Linux (openSuse 10.1)
Hi All,
I'm running Samba quite well on my OpenSuse 10.1 PPC using samba
3.0.22-13.27-1162-SUSE-CODE10 integrated with winbindd and idmap_rid
support to a Windows 2003 AD.
However, I've encountered two issues:
1. username resolution of PID UID's stay numeric, the operating system is
not resolving the UID of the process and leaving it numric.
2. in another deployment (with exact
2019 Aug 05
2
more cleanup: mis-named AD user
The saga around the misnamed DC seems over, so let's open a new thread ;-)
In the same AD I see this:
in smbstatus I see a smbd-PID for a Username "root", Group "root"
But the actual user logged in is another one. So I assume there has been
some wrong mapping/naming in the past.
I don't think that user actually runs with root-privileges or so ...
it's just ugly