Displaying 20 results from an estimated 155 matches for "piggy".
2023 Apr 28
1
gluster 10.3: task glfs_fusenoti blocked for more than 120 seconds
Good morning,
we've recently had some strange message in /var/log/syslog.
System:
debian bullseye, kernel 5.10.0-21-amd64 and 5.10.0-22-amd64
gluster 10.3
The message look like:
Apr 27 13:30:18 piggy kernel: [24287.715229] INFO: task
glfs_fusenoti:2787 blocked for more than 120 seconds.
Apr 27 13:30:18 piggy kernel: [24287.715327] Not tainted
5.10.0-22-amd64 #1 Debian 5.10.178-3
Apr 27 13:30:18 piggy kernel: [24287.715419] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" di...
2023 May 02
1
[Gluster-devel] gluster 10.3: task glfs_fusenoti blocked for more than 120 seconds
...Bert <revirii at googlemail.com> wrote:
> Good morning,
>
> we've recently had some strange message in /var/log/syslog.
>
> System:
> debian bullseye, kernel 5.10.0-21-amd64 and 5.10.0-22-amd64
> gluster 10.3
>
> The message look like:
>
> Apr 27 13:30:18 piggy kernel: [24287.715229] INFO: task
> glfs_fusenoti:2787 blocked for more than 120 seconds.
> Apr 27 13:30:18 piggy kernel: [24287.715327] Not tainted
> 5.10.0-22-amd64 #1 Debian 5.10.178-3
> Apr 27 13:30:18 piggy kernel: [24287.715419] "echo 0 >
> /proc/sys/kernel/hung_t...
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Feb 15
3
Re: Incremental Updates
As an alternative to polling the client, as Ryan describes, you could
consider piggy-backing the status updates on the back of other ajax
responses. Which way you go depends entirely on the nature of your app, in
particular:
1. how frequently it generates ajax traffic anyway
2. how long the server-side process is going to take
If the server-side process takes, say, 20 seconds,...
2007 Jun 01
2
another RFC patch: bzImage with ELF payload
...king-around patches to try
and get the linux/elf*.h headers into a bit more order, but that's not
ready yet.
J
---
arch/i386/boot/Makefile | 21 +---
arch/i386/boot/compressed/Makefile | 13 +-
arch/i386/boot/compressed/notes.S | 7 +
arch/i386/boot/compressed/piggy.S | 10 +
arch/i386/boot/compressed/vmlinux.lds | 15 ++
arch/i386/boot/compressed/vmlinux.scr | 10 -
arch/i386/boot/header.S | 4
arch/i386/boot/payload.S | 4
arch/i386/boot/setup.ld | 27 ++++-
arch/i386/boot/tools/.gitignore |...
2007 Jun 01
2
another RFC patch: bzImage with ELF payload
...king-around patches to try
and get the linux/elf*.h headers into a bit more order, but that's not
ready yet.
J
---
arch/i386/boot/Makefile | 21 +---
arch/i386/boot/compressed/Makefile | 13 +-
arch/i386/boot/compressed/notes.S | 7 +
arch/i386/boot/compressed/piggy.S | 10 +
arch/i386/boot/compressed/vmlinux.lds | 15 ++
arch/i386/boot/compressed/vmlinux.scr | 10 -
arch/i386/boot/header.S | 4
arch/i386/boot/payload.S | 4
arch/i386/boot/setup.ld | 27 ++++-
arch/i386/boot/tools/.gitignore |...
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2003 Jan 27
0
Strange error messages
.../01/27 10:48:28, 0]
printing/print_cups.c:cups_printername_ok(290)
Jan 27 10:48:28 wanda smbd[2669]: Unable to get printer status for archivi
- client-error-not-found
Jan 27 10:48:28 wanda smbd[2669]: [2003/01/27 10:48:28, 0]
smbd/service.c:make_connection(251)
Jan 27 10:48:28 wanda smbd[2669]: piggy (192.168.1.3) couldn't find
service archivi
Jan 27 10:48:29 wanda smbd[2669]: [2003/01/27 10:48:29, 0]
printing/print_cups.c:cups_printername_ok(290)
Jan 27 10:48:29 wanda smbd[2669]: Unable to get printer status for archivi
- client-error-not-found
Jan 27 10:48:29 wanda smbd[2669]: [2003/01/...
2005 Dec 11
4
Problem with acts_as_paranoid: "ArgumentError: Unknown key(s): group"
Here''s the full error:
1) Error:
test_add_message_to_existing_ticket(TicketTest):
ArgumentError: Unknown key(s): group
/usr/lib/ruby/gems/1.8/gems/activesupport-1.2.4/lib/active_support/core_ext/hash/keys.rb:48:in
`assert_valid_keys''
/usr/lib/ruby/gems/1.8/gems/acts_as_paranoid-0.2/lib/acts_as_paranoid.rb:125:in
`validate_find_options''
2012 Oct 12
5
https report processor setup
...ide some insight.
I''ve got a puppet agent and master set up and working correctly, at least
as far as I can tell. What I need to do next is get information about any
configuration changes made by the master on the agent and send it to an
external application. Ideally I would do this by piggy-backing on the
puppet reports functionality and just send the yaml reports to a remote
REST service. From everything I''ve read this should be doable, even simple.
Unfortunately that''s not the case. I''m guessing I''m missing something
basic, but I haven'...
2015 Sep 29
2
OpenCL toolset (for AMD GPU)
...clc
> (http://libclc.llvm.org/) to compile most OpenCL code.
>
> Here is an example command:
>
> clang -include /path/to/libclc/headers/clc.h -I /path/to/libclc/headers -Dcl_clang_storage_class_specifiers -target amdgcn--amdhsa -mcpu=carrizo $INPUT_FILE -o $OUTPUT_FILE
Hi Tom,
to piggy-pack on this question. To load this kernel in OpenCL, is it sufficient to just pass $OUTPUT_FILE
to clCreateProgramWithBinary?
Also, assuming this is enough. Is the code quality for recent AMD GPUs quality-wise on the level of what AMD's closed-source driver would generate.
Thank you,
Tobias
2006 Jun 30
2
Rather ominous resource consumption figures
Hello,
Yesterday I posted about how to email from a worker. I decided to be a bit
piggy and just inhale all of rails. Sorted. I am noticing some rather
ominous behavior though.
The setup: My worker takes an uploaded image as a param and passes it (via
system call) to a C++ image processing engine. Take a look at these memory
consumption figures for successive runs uploading the ident...
2007 Apr 03
2
are memory limits on mongrel possible?
Is there any documentation I can look at that might talk about how to
put
memory limits on mongrel? For instants, I might want to limit mongrel to
100 megs of ram. I know that I can monitor mongrel with monit and
restart it
automatically if it becomes a ram piggy.
1998 Apr 01
0
SAMBA digest 1621
...gt; Systems and networks adm.
>
>
Didier
Yes, I have downloaded and experimented with the NTDOM branch of
samba. As you said, their goals are to make a full domain controller
in which user addresses and profiles are given out by the Samba server.
What my patch did for me was allow me to piggy back off of the
corporate NT domain controller. I am not the administrator of that
controller and have no admin rights to the domain.
I also don't want to go to all of the hassles of maintaining a domain.
So i have piggy backed my Samba server to the corporate controller.
I published some s...
2007 Jan 12
5
Rails session parasite...
All,
I see this item on the merb-0.0.8 release notes
Added rails session parasite mode.
I am assuming merbs can piggy back off the rails current session.
How does one achieve that ?
Thanks
Fernand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/merb-devel/attachments/20070112/0803f46e/attachment.html