similar to: LXC and syslog seperation (/dev/log)

I've implemented a patch to openssh which allows the PAM auth layer to detect if the PAM stack has changed the user name and then adjusts its internal data structures accordingly. (imagine a PAM stack that uses individual credentials to authenticate, but assigns the user to a role account). First, is the openssh community interested in this patch? Second, if there is interest in the patch,

On Fri, Apr 10, 2015 at 08:09:58AM -0500, James Leu wrote: > Hello, > > I'm seeing syslog messages "bleed" from the host and other LXC into > the messages, maillog, secure logs of other LXCs. > > I'm using libvirt 1.0.0 on a host with systemd and kernel 3.9.10. > Each LXC is running an older non-systemd linux distribution > > Is this a known issue?

Hello, I'm using libvirt to build/run LXC instances. My LXC instances use passthrough filesystem mounts. When I try to do large file systems operations (ex tar or rsync) the file systems cache on the host spikes and causes the OOM handler to run and kills processes in the LXC. Has anyone else seen this? Is there a way around this? At this point I'm resorting to running a cron job that

http://bugzilla.mindrot.org/show_bug.cgi?id=1215 Jesse Zbikowski <embeddedlinuxguy at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |embeddedlinuxguy at gmail.com --- Comment #7 from Jesse Zbikowski <embeddedlinuxguy at

my goal for testing/simulations is to be able to run a vm on my desktop and within that vm run linux containers currently I can start an ubuntu trusty vm using libvirt as my broker to qemu or qemu-system-x86_64 directly and start a saucy-based lxc using lxc-tools. I invoke lxc-start -n name -f configfile and within a few seconds I'm logged into my saucy based lxc. I can't start the lxc

On 07/15/2014 08:29 AM, Robb Walker wrote: > Just another ping, and please let me know if this is not the proper format to re-ask my submitted question, but anyone else having any joy on running lxcs via libvirt launched from within a vm? This is the right forum, even if no one has answered so far. Running lxc guests inside an L1 kvm guest should be possible (I haven't tried it myself,

Something has killed any writes to /var/log/messages. Syslogd is running. Has been off for some time and I just discovered it. Any hints as to what / where to look since syslogd is running? Sam -- Sam W.Drinkard -- sam at wa4phy.net NOAA Cooperative Observer KAGS (snow) http://wa4phy.net Augusta Area Mesonet

On 7/24/2017 8:39 PM, Nico Kadel-Garcia wrote: > > Why are the targets of the hardlinks evaporating on rebooting? Is that > a FreeBSD'ism? Its when syslogd stops/starts. The hardlinks need to be recreated for some reason. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike at sentex.net Providing Internet services since 1994

http://bugzilla.mindrot.org/show_bug.cgi?id=906 Summary: syslog messages from sshd [net] lost Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: peak at

Thanks for the info. Did you create unprivileged containers to run Samba in? On Wed, Jun 3, 2015 at 6:02 PM, John Lewis <oflameo2 at gmail.com> wrote: > I have my deployment of Version 4.1.17-Debian in a Debian container. I > pretty much a standard system container with Samba installed. I run two > of them in a virtual network on a VPS as Domain controllers. Each > instance is

Hy! I receive an nxge driver messages on console: Aug 18 11:08:42 [hostname] nxge: NOTICE: nxge_ipp_eccue_valid_check: rd_ptr = XXX wr_ptr = YYY I find the bug description/correction at sun web page, and i know i can ignore it. I thinking about how can i delete from console only these messages (here is my first version, what is not (so) elegant): #!/usr/sbin/dtrace -qs #pragma D option

Maybe one of you can help. We have set up a CentOS server so that each user who logs in via sftp will be jailed in their home directory. Here's the relevant sshd_config: # override default of no subsystems Subsystem sftp internal-sftp -f LOCAL2 -l INFO Match Group sftponly ChrootDirectory /home/%u ForceCommand internal-sftp This actually works great, but none of

When I compile this program *$ cat vararg1-main.c typedef struct { double d; } S0; S0 g1; void foo0(int a, ...); int main(int argc, char **argv) { S0 s0 = { 2.0 }; foo0(1, s0); printf("%f\n", g1.d); * * return 0; }* with this command, *$ clang -target arm-none-linux-gnueabi-gcc -ccc-clang-archs armv7 -emit-llvm vararg1-main.c -S -o vararg1-main.ll -O3* I get this

Hello, I've started working with samba4-alpha6. I've been successful in setting up an AD with an openldap backend. I'm now shifting my focus to how I would go about migrating to a samba4 setup from a microsoft AD implementation. To that end I've written a perl script that uses Net::LDAP to create users in the samba4 LDAP backend. I can create the user in such a way that samba4

Yes, I see the load is 8-byte aligned in the bit code. My question was, assuming that arguments requiring double word alignment have to be passed in even/odd registers, how does the backend know that %0 has to be passed in register r2 and r3? *tail call arm_aapcscc void (i32, ...)* @foo0(i32 1, [2 x i32] %0) nounwindt * It doesn't seem that ARM backend can figure out that "[2 x i32]

On Aug 6, 2012, at 3:21 PM, Akira Hatanaka <ahatanak at gmail.com> wrote: > When I compile this program > > $ cat vararg1-main.c > > typedef struct { > double d; > } S0; > > S0 g1; > > void foo0(int a, ...); > > int main(int argc, char **argv) { > S0 s0 = { 2.0 }; > > foo0(1, s0); > > printf("%f\n", g1.d); >

See ARMCallingConv.td:113. The alignment of the arg is checked and if it's 8-byte aligned, the proper registers are chosen. deep On Tue, Aug 7, 2012 at 1:20 AM, Akira Hatanaka <ahatanak at gmail.com> wrote: > Yes, I see the load is 8-byte aligned in the bit code. > > My question was, assuming that arguments requiring double word alignment > have to be passed in even/odd

Anyone having problems with logrotate and CentOS 5.4? Although I have /etc/logrotate.d/mail (contents below) to rotate my maillog file, it fails to do it automatically: /var/log/maillog { compress dateext maxage 365 rotate 60 size=+1024k missingok postrotate /etc/init.d/MailScanner restart endscript } ++++++++++++++++++++++++++++ logrotate.conf:

Hi, although I've done S3 dispatching for more than a decade now, I think I managed to overlook/avoid the following pitfall when using NextMethod(): If you explicitly pass argument '...' to NextMethod(), you will effectively pass those argument twice to the "next" method! EXAMPLE: foo0 <- function(...) UseMethod("foo0"); foo1 <- function(...)

I checked most samba 4 related posts and couldn't fine the answer. Is there any targeted date for samba4 to become stable? thanks, Ying