search for: sys_

...n"; - print OUT "\n"; - print OUT "\t.text\n"; - print OUT "\t.align 4\n"; - print OUT "\t.globl ${name}\n"; - print OUT "\t.type ${name},\@function\n"; - print OUT "${name}:\n"; - print OUT "\tpushl \$SYS_\U${name}\n"; - print OUT "\tjmp __socketcall_common\n"; - print OUT "\t.size ${name},.-${name}\n"; - close(OUT); - } else { - open(OUT, "> ${outputdir}/${name}.c") - or die "$0: Cannot open ${outputdir}/${name}.c\n"; - - print OUT...

Hi all, I want to use llvm to analyze the dependency between the system call fuction( defined like sys_**() ) by analyze its read and write data type. I'm a new in using llvm to statically analyze the C souce code. I have learned how to write Pass and searched some materials for a month, but didn't know exactly how to do it. I have some troubles, it's very kind of you to give me some help...

Attached is a patch for Swig that at least allows us to link the library. I am experiencing a number of bugs that will need to be tracked down and squashed. I haven''t even had time to look at the newer Swig features yet. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

I have a define that looks like this: define user::sys_user($fullname, $uid, $groups, $shell=''/bin/bash'', $authkey, $authkey_type=rsa) { $username = "sys_${name}" group { $username: gid => $uid, } user { $username: require => Group[$username],...

...2.2.8a There is possible deadlock in smbmount (smbmount.c) when parent process forking. Maybe this is a Linux-only bug (2.4 and 2.6 shows the same). But this is enough to apply my patch (or make other proper thing[s]). Explaining: Smbmount need to be a daemon to serve the mountpoint. Parent make [sys_]fork() to create this young daemon. After sys_fork() children go ahead and kill(parentpid, SIGTERM). BUT! Parent sometimes late to finish his sys_fork() :(( I don't know why. And when he still in fork() and children kill(perentpid,SIGTERM)'s him parent calls exit(), but after this begin som...

...a specific log level set, so I'm just using whatever the default log level is. But, in the code I can see that these messages are logged with debug level 0, so they would appear regardless of what my log level was. DEBUG(0,(__location__ ": Failed DNS update - with error code %d\n", sys_ errno)); On 23 September 2016 at 15:22, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Fri, 23 Sep 2016 15:11:21 +0100 > Jonathan Hunter <jmhunter1 at gmail.com> wrote: > > > Thank you Rowland. > > > > I have a couple of reverse zones (diff...

...nt, int, int, int *); diff --git a/usr/klibc/accept.c b/usr/klibc/accept.c new file mode 100644 index 0000000..3ae7bcd --- /dev/null +++ b/usr/klibc/accept.c @@ -0,0 +1,16 @@ +/* + * pread.c + * + * Some architectures need to wrap the system call + */ + +#include <sys/socket.h> + +#if !_KLIBC_SYS_SOCKETCALL && defined(__NR_accept4) && !defined(__NR_accept) + +int accept(int socket, struct sockaddr *address, socklen_t *addr_len) +{ + return accept4(socket, address, addr_len, 0); +} + +#endif diff --git a/usr/klibc/socketcalls.pl b/usr/klibc/socketcalls.pl index 9df5949..70ded0...

Thank you Rowland. I have a couple of reverse zones (different subnets across sites), yes, these are in Samba AD/DNS as well. Where are you looking in the logs - I'm missing seeing the bit that shows an update happening then failing? I tried tcpdump to find out what the query was that was failing, but I couldn't see any updates, just queries :( On 23 September 2016 at 14:56, Rowland

...oblems. converting the current LDAP tree was also no problem. everything was fine and very fast. the first problem i saw was an error when logging of from a windows2000-SP4 domain member. the profile data wasn't written back. the logfile shows a "PANIC" line like this: - -> PANIC: sys_[sg]et_vfs_quota: called with NULL pointer sorry, don't know if it was "set" or "get". i recompiled samba without --with-sys-quotas and everything was fine again. the next problem i saw was another error message in the log's similar to #281 in bugzilla the complete messa...

...But this is still a file system: we don''t get rollback if things go wrong. Instead, do what we can up front to make sure things will work out. And if things do go wrong, optionally prevent a partial result from reaching the disk. A few things: - The implementation just exports the sys_* calls it needs (a popular move, no doubt :). I''ve looked at using the corresponding vfs_* instructions instead, and keeping a table of struct file *''s instead of fd''s to avoid these exports, but this requires a large amount of duplication of semi-boilerplate path lo...