search for: 128s

...tion I want, it gives me a warning. # parted /dev/sda "mklabel gpt" Warning: The existing disk label on /dev/sda will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? yes # parted -a optimal /dev/sda "mkpart primary 128s -1s" Warning: You requested a partition from 65.5kB to 81.0TB. The closest location we can manage is 65.5kB to 81.0TB. Is this still acceptable to you? Yes/No? yes Warning: The resulting partition is not properly aligned for best performance. Ignore/Cancel? i...

...MB (Ethernet), snapshot length 262144 bytes 10:23:07.468629 IP (tos 0x0, ttl 128, id 22607, offset 0, flags [none], proto UDP (17), length 96) 192.168.0.53.ntp > mail.hprs.local.ntp: NTPv3, Client, length 68 Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 7 (128s), precision -23 Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) Reference Timestamp: 3916127270.315146199 (2024-02-05T13:07:50Z) Originator Timestamp: 0.000000000 Receive Timestamp: 0.000000000 Transmit Timestamp: 3916480...

...apshot length 262144 bytes > 10:23:07.468629 IP (tos 0x0, ttl 128, id 22607, offset 0, flags [none], proto UDP (17), length 96) > 192.168.0.53.ntp > mail.hprs.local.ntp: NTPv3, Client, length 68 > Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 7 (128s), precision -23 > Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) > Reference Timestamp: 3916127270.315146199 (2024-02-05T13:07:50Z) > Originator Timestamp: 0.000000000 > Receive Timestamp: 0.000000000 >...

From: "Richard W.M. Jones" <rjones at redhat.com> This reverts commit a9c8123c72db47bcab8dd738e8d5256a9ae87f11. --- daemon/file.c | 18 +++--------------- daemon/parted.c | 3 +-- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/daemon/file.c b/daemon/file.c index 057e15d..91746e0 100644 --- a/daemon/file.c +++ b/daemon/file.c @@ -525,7 +525,7 @@

...+ mk_ipaddr(&gip, pkt->gip), + printf( + "opcode: %u Hardware: %u Hardlen: %u Gatehops: %u ident: %08x\n" + "seconds: %u Flags: %u cip: %s yip: %s\n" + "sip: %s gip: %s\n" + "Sname: %.64s\n" + "bootfile: %.128s\n", + pkt->opcode, + pkt->Hardware, + pkt->Hardlen, + pkt->Gatehops, + pkt->ident, + pkt->seconds, + pkt->Flags, + cip.v, + yip.v, + sip.v, + gip.v, + pkt->Sname, + pkt->bootfi...

Are your clients talking to the DCs re. Time at all ? This is an example in one of my DCs: Run tcpdump on your DC: root at dwing:~# tcpdump??port 123 -v tcpdump: listening on enp1s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:20:41.655081 IP (tos 0x0, ttl 128, id 32113, offset 0, flags [none], proto UDP (17), length 96) ?? ?192.168.3.52.ntp > dwing.mad.mater.int.ntp: NTPv3,

nuqneH, I've tried using TIS authsrv authentication via bsd auth and found it quite limited. The most important restriction it does not log ip and fqdn of the remote peer, nor the application name, to the authentication server. It does not matter much for TIS authsrv, but since other applications do provide such information, our authsrv version uses it for extra authentication restrictions.

I am rebasing Fedora rawhide oprofile package to oprofile-0.9.7. The xenoprof patches on http://xenoprof.sourceforge.net/#download look a bit dated. The newest version is for oprofile-0.9.5. I massaged the patch oprofile-0.9.5-xen.patch to apply to oprofile-.0.9.7. Attached is that updated patch. Does this look reasonable? Is there a desire to get this into upstream oprofile? Or should the

...guestfs: send_to_daemon: 64 bytes: 00 00 00 3c | 20 00 f5 f5 | 00 00 00 04 | 00 00 00 d2 | 00 00 00 00 | ... guestfsd: main_loop: new request, len 0x3c /dev/sda: No such file or directory udevadm settle udevadm: No such file or directory udevsettle parted -s -- /dev/vda mklabel msdos mkpart primary 128s -128s udevadm settle udevadm: No such file or directory udevsettle guestfsd: main_loop: proc 210 (part_disk) took 1.16 seconds libguestfs: recv_from_daemon: 40 bytes: 20 00 f5 f5 | 00 00 00 04 | 00 00 00 d2 | 00 00 00 01 | 00 12 34 00 | ... libguestfs: send_to_daemon: 84 bytes: 00 00 00 50 | 20 00...

...00 00 00 3c | 20 00 f5 f5 | 00 > 00 00 04 | 00 00 00 d2 | 00 00 00 00 | ... > guestfsd: main_loop: new request, len 0x3c > /dev/sda: No such file or directory > udevadm settle > udevadm: No such file or directory > udevsettle > parted -s -- /dev/vda mklabel msdos mkpart primary 128s -128s > udevadm settle > udevadm: No such file or directory > udevsettle > guestfsd: main_loop: proc 210 (part_disk) took 1.16 seconds > libguestfs: recv_from_daemon: 40 bytes: 20 00 f5 f5 | 00 00 00 04 | 00 > 00 00 d2 | 00 00 00 01 | 00 12 34 00 | ... > libguestfs: send_to_dae...

...00 >> 00 00 04 | 00 00 00 d2 | 00 00 00 00 | ... >> guestfsd: main_loop: new request, len 0x3c >> /dev/sda: No such file or directory >> udevadm settle >> udevadm: No such file or directory >> udevsettle >> parted -s -- /dev/vda mklabel msdos mkpart primary 128s -128s >> udevadm settle >> udevadm: No such file or directory >> udevsettle >> guestfsd: main_loop: proc 210 (part_disk) took 1.16 seconds >> libguestfs: recv_from_daemon: 40 bytes: 20 00 f5 f5 | 00 00 00 04 | 00 >> 00 00 d2 | 00 00 00 01 | 00 12 34 00 | ... >...

On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 04:30:37PM +0800, Zhi Yong Wu wrote: >> HI, >> >> On a RHEL5 box, i tried to directly run guest which was issued by >> libguestfs virt-xxx commands as below. But after some minutes, it >> exited exceptionally. >> >> Does anyone also hit the

...hannel '/dev/virtio-ports/org.libguestfs.channel.0' udevadm settle libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [05013ms] appliance is up Guest launched OK. guestfsd: main_loop: new request, len 0x3c udevadm settle parted -s -- /dev/sda mklabel msdos mkpart primary 128s -128s Warning: The resulting partition is not properly aligned for best performance. udevadm settle guestfsd: main_loop: proc 210 (part_disk) took 0.39 seconds guestfsd: main_loop: new request, len 0x50 wipefs --help wipefs -a /dev/sda1 mke2fs -t ext2 -F /dev/sda1 mke2fs 1.42.8 (20-Jun-2013) guestf...

...annel '/dev/virtio-ports/org.libguestfs.channel.0' udevadm settle libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [264424ms] appliance is up Guest launched OK. guestfsd: main_loop: new request, len 0x3c udevadm settle parted -s -- /dev/sda mklabel msdos mkpart primary 128s -128s Warning: The resulting partition is not properly aligned for best performance. udevadm settle guestfsd: main_loop: proc 210 (part_disk) took 1.94 seconds guestfsd: main_loop: new request, len 0x50 wipefs --help wipefs -a --force /dev/sda1 mke2fs -t ext2 -F /dev/sda1 mke2fs 1.42.8 (20-Jun-2013...

...d GUESTFS_LAUNCH_FLAG libguestfs: [03797ms] appliance is up Guest launched OK. libguestfs: send_to_daemon: 64 bytes: 00 00 00 3c | 20 00 f5 f5 | 00 00 00 04 | 00 00 00 d2 | 00 00 00 00 | ... guestfsd: main_loop: new request, len 0x3c udevadm settle parted -s -- /dev/sda mklabel msdos mkpart primary 128s -128s [ 2.660292] sda: [ 2.672719] sda: sda1 Warning: The resulting partition is not properly aligned for best performance. udevadm settle libguestfs: recv_from_daemon: 40 bytes: 20 00 f5 f5 | 00 00 00 04 | 00 00 00 d2 | 00 00 00 01 | 00 12 34 00 | ... libguestfs: send_to_daemon: 84 bytes:...

...stfs: send_to_daemon: 64 bytes: 00 00 00 3c | 20 00 f5 f5 | 00 00 00 04 | 00 00 00 d2 | 00 00 00 00 | ... guestfsd: main_loop: new request, len 0x3c /dev/sda: No such file or directory udevadm settle udevsettle udevsettle: No such file or directory parted -s -- /dev/vda mklabel msdos mkpart primary 128s -128s [ 3.166588] vda: [ 3.167922] vda: vda1 Warning: The resulting partition is not properly aligned for best performance. udevadm settle udevsettle udevsettle: No such file or directory guestfsd: main_loop: proc 210 (part_disk) took 0.08 seconds libguestfs: recv_from_daemon: 40 bytes: 20...

On Thu, Jun 12, 2014 at 05:08:37PM +0530, abhishek jain wrote: > Hi Rich > > I have all the virtio modules available in the kernel but I'm getting the > same result . It doesn't appear to be using any kernel modules. I would have expected to see output such as this: supermin: internal insmod virtio.ko It seems as if you might not be setting SUPERMIN_MODULES; or maybe you

Unfortunately, placing the link into the /boot does not work. libguestfs-test-tool failes with the same message: ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *

...hannel '/dev/virtio-ports/org.libguestfs.channel.0' udevadm settle libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [25908ms] appliance is up Guest launched OK. guestfsd: main_loop: new request, len 0x3c udevadm settle parted -s -- /dev/sda mklabel msdos mkpart primary 128s -128s Warning: The resulting partition is not properly aligned for best performance. udevadm settle guestfsd: main_loop: proc 210 (part_disk) took 1.42 seconds guestfsd: main_loop: new request, len 0x50 wipefs --help wipefs -a /dev/sda1 mke2fs -t ext2 -F /dev/sda1 mke2fs 1.42.9 (4-Feb-2014) guestfs...

...nnel.0' udevadm --debug settle calling: settle libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [14482ms] appliance is up Guest launched OK. guestfsd: main_loop: new request, len 0x3c udevadm --debug settle calling: settle parted -s -- /dev/sda mklabel msdos mkpart primary 128s -128s Warning: The resulting partition is not properly aligned for best performance. udevadm --debug settle calling: settle guestfsd: main_loop: proc 210 (part_disk) took 0.86 seconds guestfsd: main_loop: new request, len 0x50 wipefs --help wipefs -a --force /dev/sda1 mke2fs -t ext2 -F /dev/sda1 mk...