Displaying 8 results from an estimated 8 matches for "ipc_init".
Did you mean:
i2c_init
2005 Sep 19
1
pam and sasl2-sample-server failure
...---------------
# saslauthd -m /var/run/saslauthd -a pam -d
saslauthd[3176] :main : num_procs : 5
saslauthd[3176] :main : mech_option: NULL
saslauthd[3176] :main : run_path : /var/run/saslauthd
saslauthd[3176] :main : auth_mech : pam
saslauthd[3176] :ipc_init : using accept lock file:
/var/run/saslauthd/mux.accept
saslauthd[3176] :detach_tty : master pid is: 0
saslauthd[3176] :ipc_init : listening on socket:
/var/run/saslauthd/mux
saslauthd[3176] :main : using process model
saslauthd[3177] :get_accept_lock : acquired accept...
2004 Oct 23
0
win32-ipc, with blocks (code review please)
...**************************
* ipc.c - source for the win32-ipc package
****************************************************************************/
#include "ruby.h"
#include <windows.h>
#include "ipc.h"
static VALUE cIpcError;
static char error[MAX_STRING];
static VALUE ipc_init(VALUE self, VALUE obj){
IpcStruct* ptr;
Data_Get_Struct(self,IpcStruct,ptr);
ptr->handle = (HANDLE)NUM2UINT(obj);
return self;
}
static VALUE ipc_allocate(VALUE klass){
IpcStruct* ptr = malloc(sizeof(IpcStruct));
return Data_Wrap_Struct(klass,0,ipc_free,ptr);
}
static VALUE w...
2009 Aug 26
3
saslauthd
...main : num_procs : 5
saslauthd[1936] :main : mech_option: /usr/lib64/sasl2/smtpd.conf
saslauthd[1936] :main : run_path : /var/run/saslauthd
saslauthd[1936] :main : auth_mech : shadow
saslauthd[1936] :detach_tty : master pid is: 0
saslauthd[1936] :ipc_init : listening on socket:
/var/run/saslauthd/mux
saslauthd[1936] :main : using process model
saslauthd[1936] :have_baby : forked child: 1937
saslauthd[1936] :have_baby : forked child: 1938
saslauthd[1936] :have_baby : forked child: 1939
saslauthd[1936] :have_baby...
2009 Nov 03
2
Zimbra help?
...id
Nov 2 17:57:28 indie postfix/postfix-script[9308]: starting the Postfix mail system
Nov 2 17:57:28 indie postfix/master[9309]: fatal: bind 0.0.0.0 port 25: Address already in use
Nov 2 17:57:28 indie saslauthd[9316]: detach_tty : master pid is: 9316
Nov 2 17:57:28 indie saslauthd[9316]: ipc_init : listening on socket: /opt/zimbra/cyrus-sasl-2.1.23.3z/state/mux
Nov 2 17:57:28 indie zimbramon[2574]: 2574:info: Starting stats via zmcontrol
Nov 2 17:57:59 indie zmmailboxdmgr[10822]: status requested
Nov 2 17:57:59 indie zmmailboxdmgr[10822]: status OK
Nov 2 17:57:59 indie zmmailbo...
2004 Nov 04
4
Attempt to build a gemspec
Hi all,
I''m trying to build a gemspec for win32-ipc, using a precompiled binary.
Here''s my gemspec file:
#win32-ipc.gemspec
require "rubygems"
spec = Gem::Specification.new do |s|
s.name = "win32-ipc"
s.version = "0.3.1"
s.platform = Gem::Platform::WIN32
s.summary = "A base class for Win32 synchronization
objects."
2011 Jun 13
5
3.0.0-rc2: Xen: High amount of kernel "reserved" memory, about 33% in 256MB DOMU
Hi,
another issue I''m seeing with 3.0-rc2 and Xen is that there is an
unexpectedly high amount of kernel reserved memory.
I suspect that Linux allocates page table entries and corresponding
data structures for the whole 6GB areas of the provided ''physical
RAM map'' even though it has rather big unusable holes in it.
[ 0.000000] BIOS-provided physical RAM map:
[
2010 Nov 16
0
Bug#603727: xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver)
...turned 0 after 5 usecs
[ 38.379277] calling init_ramfs_fs+0x0/0xa @ 1
[ 38.383784] initcall init_ramfs_fs+0x0/0xa returned 0 after 0 usecs
[ 38.390110] calling init_hugetlbfs_fs+0x0/0x7c @ 1
[ 38.395102] initcall init_hugetlbfs_fs+0x0/0x7c returned 0 after 48 usecs
[ 38.401897] calling ipc_init+0x0/0x1c @ 1
[ 38.406057] msgmni has been set to 1411
[ 38.409959] initcall ipc_init+0x0/0x1c returned 0 after 3811 usecs
[ 38.416196] calling ipc_sysctl_init+0x0/0xd @ 1
[ 38.420892] initcall ipc_sysctl_init+0x0/0xd returned 0 after 14 usecs
[ 38.427462] calling init_mqueue_fs+0x0/0x93...
2016 Mar 22
19
[PATCH v3 0/11] tests/qemu: Add program for tracing and analyzing boot times.
Lots of changes since v2, too much to remember or summarize.
Please ignore patch 11/11, it's just for my testing.
Rich.