search for: start_names

Any ideas folks? Thanks, Dan ---------- Forwarded message ---------- From: Kay <serphakay at hotmail.com> Date: Sep 19, 2007 10:52 AM Subject: win32-service of win32utils To: djberg96 at gmail.com I''m writing some scripts to programmatically change the user account of running a windows service. So I downloaded one of the windows utilities, win32-service, and wrote my scripts.

Ah, excellent. Glad you got it figured out! Regards, Dan Yuhong Liu wrote: > Hi Dan, > > I think I have figured out the problem. The issue is because of the > setting of service type. So by default the service type is set as > Service::WIN32_OWN_PROCESS | Service::INTERACTIVE_PROCESS. This means > the service is configured to interact with the desktop, you cannot >

...llvm_prf_names; +extern char __stop___llvm_prf_names; + +static void *start_data = &__start___llvm_prf_data; +static void *end_data = &__stop___llvm_prf_data; +static void *start_counters = &__start___llvm_prf_cnts; +static void *end_counters = &__stop___llvm_prf_cnts; +static void *start_names = &__start___llvm_prf_names; +static void *end_names = &__stop___llvm_prf_names; + +static void reset_counters(void) +{ + memset(start_counters, 0, end_counters - start_counters); +} + +static uint32_t get_size(void) +{ + return ROUNDUP(sizeof(struct llvm_profile_header) + end_data -...

Hi Ernest, I''m cc''ing the win32utils-devel mailing list in case anyone has any ideas. --- Ernest Ellingson <erne at powernav.com> wrote: > Daniel Berger wrote: > > >Hi Ernest, > > > >Me again. I just realized that it''s just a bug in > my > >documentation (duh). You can pass arguments to the > >Service.start method.

Hello, The following patch series enables LLVM coverage support for the Xen hypervisor. This first patches are a re-organization of the gcov support, in order to make the support generic for all coverage technologies. This is mostly a name change from gcov -> cov in several places and files, together with the addition of a Kconfig option in order to enable LLVM coverage. Patch 7 introduces

Besides supporting newer version of xfs file system, this patch also does some code refactoring and fix completely broken listing and searching on v2-3 node directories. Cc: Gene Cumm <gene.cumm at gmail.com> Cc: H. Peter Anvin <hpa at zytor.com> Cc: Raphael S. Carvalho <raphael.scarv at gmail.com> Cc: Ady <ady-sf at hotmail.com> Signed-off-by: Paulo Alcantara <pcacjr

xfs_is_valid_magicnum is not actually a generic function that checks for magic numbers, instead it checks only for superblock's one. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- core/fs/xfs/xfs.c | 13 +++++-------- core/fs/xfs/xfs.h | 19 ++++++++++--------- 2 files changed, 15 insertions(+), 17 deletions(-) diff --git a/core/fs/xfs/xfs.c b/core/fs/xfs/xfs.c index

This pull request contains the XFS filesystem driver for Syslinux. Due to historical reasons (SGI IRIX's design of disk layouts), the first sector in the primary AG on XFS filesystems contains the superblock, which is a problem with BIOSes, since VBRs must be loaded up from the first sector of the active partition. Thus, we needed to handle this issue by putting the Syslinux bootsector

I found a small (easily worked around) bug in service.c. The accessor for the start user is called "start_name", but create_service tries to access "@service_start_name". A simple "service.instance_eval{@service_start_name = ''name''} works around it, but I thought ya''ll might want to fix it. BTW, thanks for win32-utils... I don''t like