similar to: Abuse of the syslog facility

Define more syslog flags that are still ignored: diff -uNr klibc-0.188/include/syslog.h udev-040/klibc-0.188/include/syslog.h --- klibc-0.188/include/syslog.h 2003-11-23 14:46:23.000000000 -0700 +++ udev-040/klibc-0.188/include/syslog.h 2004-10-21 15:35:22.411495112 -0600 @@ -47,6 +47,14 @@ #define LOG_FACMASK 01770 #define LOG_FAC(x) (((x) >> 3) & (LOG_FACMASK

On 11 May 2018 at 23:53, Jeremy Allison <jra at samba.org> wrote: > On Fri, May 11, 2018 at 09:33:15PM +0100, Rowland Penny via > samba-technical wrote: > > On Fri, 11 May 2018 13:17:52 -0700 > > Jeremy Allison <jra at samba.org> wrote: > > > > > On Fri, May 11, 2018 at 09:56:47PM +0200, Timur I. Bakeyev via samba > > > wrote: > > >

I wrote this little program to deal with the situation where there are a number of workgroups on a number of subnets with no WINS server [actually I couldn't get this configuration to run with a WINS server - but that's another story] You run this program on machines bridging your subnets and it listens for netbios nameserver packets and forwards them. [Broadcast packets are sent on to

Wondering if anyone here might better be able to diagnose an issue we're seeing, or point me to some guidelines for this sort of thing. There are two machines with identical hardware, both running Red Hat 7.3's stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these:

Hi All, I m a novice developer of Linux applications. Recently I faced a file system corruption. (I guess) I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. EXT3-fs error (device ide0(3,2)):

On Fri, 11 May 2018 13:17:52 -0700 Jeremy Allison <jra at samba.org> wrote: > On Fri, May 11, 2018 at 09:56:47PM +0200, Timur I. Bakeyev via samba > wrote: > > > > > Fixing it in both ways is easy, but it would be nice to hear from > > the developers, why did they choose such a limited set of syslog > > facilities. > > I don't know. The limited

Apologies for cross posting but some of us aren't on the other list (vice/versa) and thought both groups would benefit. For those familiar with the VoIP Abuse Project, no need to explain the gist of this. I got tired of parsing through the alerts (lists) I receive via email daily. They're long and sometimes I don't have the time to post them all. So for now, posting VoIP Abuse

-------------- next part -------------- A non-text attachment was scrubbed... Name: abuse.pdf Type: application/pdf Size: 3600 bytes Desc: not available Url : http://lists.linux-foundation.org/pipermail/virtualization/attachment= s/20070726/e09498ee/abuse.pdf

Would the person(s) who is reporting the occasional spam messages relayed through this list to Spamcop please refrain from doing so, or unsubscribe? You were warned that the list is open when you subscribed *and* that a small amount of spam would make it through as a result. As a result of this: my friend, who has generously dontated the use of a co-located server to act as a relay for this

Matt, Sourceforge.net is exclusively for hosting software whose licensing terms meet the OSI's definition of Open Source: http://opensource.org/docs/definition.php Your licensing terms include the following, which is not compliant with the OSI definition: Usage Restrictions In addition to the restrictions of the LGPL, the following restrictions apply: ... OrderlyCalls may not be

By popular request, we've convinced someone from the VoIP Abuse Project to join us tomorrow at noon on VUC. I think many of you will be interested in this topic, so please come by, join in and ask questions. http://vuc.me for all connection info and links to VoIP Abuse Project A couple of other features and announcements are scheduled after that segment, including an Astricon update and

pte_index is an internal arch helper in various architectures, without consistent semantics. Open code that calculation of a PMD index based on the virtual address instead. Signed-off-by: Christoph Hellwig <hch at lst.de> --- mm/hmm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/hmm.c b/mm/hmm.c index 03d37e102e3b..2083e4db46f5 100644 --- a/mm/hmm.c +++

***** This an automatic response to confirm that we have received your recent report regarding a Network Abuse or Security incident involving an IKANO Communications Branded partner, and are taking the following actions to resolve the issue. ***** The subject of your e-mail was: Postmaster, &#288;&#279;&#355; ready for

You are receiving this reply because you just emailed one of us at EDSON Internet and we are protecting ourselves from receiving junk mail. Please read the below, action is required on your part: Edson Internet has been in business for over 10 years and because of that we get over 4000 junk mails a day! Therefore, we have implemented this system to be more responsive to you. I hope you will

Here is my log from 'make check' using an Intel i5 64-bit processor - http://pastebin.com/raw/N6SYAuFX Here is Isaac's log from 'make check' using an Intel Atom 32-bit processor - http://pastebin.com/raw/sey6DEk9 We are both on Alpine Linux, which uses the musl libc. http://www.musl-libc.org/ Thank you very much. On Thu, Jan 28, 2016 at 9:54 AM, Alba Pompeo <albapompeo

This has come up before, and we just added -fwrapv to work around the problem: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110131/115969.html Are you compiling without -fwrapv? Cameron On May 6, 2013, at 4:55 PM, Shuxin Yang <shuxin.llvm at gmail.com> wrote: > Hi, There: > > Clang fails to compile 254.gap @ CPU2000int suite. The symptom is that executable

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1044: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Karol Herbst <kherbst at redhat.com> Cc: Lyude Paul <lyude at redhat.com> Cc: David Airlie <airlied

This takes advantage of glibc's MALLOC_PERTURB_. If you develop on glibc-based systems and don't yet set this via your shell's init scripts, add something like this to e.g., .bashrc: export MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) This change ensures that it's enabled for anyone running "make check" and in particular for koji. There's probably documentation

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1044: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst Signed-off-by: Lee Jones <lee at kernel.org> --- Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Karol Herbst <kherbst at redhat.com> Cc: Lyude Paul

Package: logcheck-database Version: N/A Severity: normal Hello, As announced in http://lists.debian.org/debian-devel/2006/09/msg00630.html, this bug report is part of a mass bug filing campaign about the "abuse" of debconf templates of type "note". First of all, in case you fixed you package in the short timeframe that happned between my announcement and this bug report,