search for: targetfil

...gt;> /tmp/unpack.log"); $from = substr $from, 0, index($from, ' ') ; ? ## Enable the sections you want to use below only create a pdf is enable. # *********************** start inputfile = pdf *********************** @files = </tmp/$RANDOM/*.pdf>; foreach $file (@files) { ?? $targetfile = substr $file, rindex($file, '/') + 1; ?? system ("/usr/bin/pdftk $file output /tmp/$targetfile 2>/dev/null"); ?? system("/usr/bin/mpack -s \"Re: $subject\" -d /home/msg/message.msg \"/tmp/$targetfile\" \"$from\""); ?? system("rm -...

This changes the infrastructure to allow the target_file to be a QEMU URI. Rich.

...=============================== --- src/library/tools/R/Rd2HTML.R (revision 50178) +++ src/library/tools/R/Rd2HTML.R (working copy) @@ -305,7 +305,7 @@ if (!OK) { ## so how about as a topic? file <- utils:::index.search(parts$targetfile, pkgpath) - if (nzchar(file)) { + if (length(file)>0 && nzchar(file)) { warnRd(block, Rdfile, "file link ", sQuote(parts$targetfile), " in packag...

...I noticed that because the block device was deleted, the next run overwrote it with a file. * It was not documented anywhere how to do it. This commit makes the small code change needed to allow virt-v2v to write to a block device, only for existing outputs which write to local files (ie. using TargetFile). Also it avoids deleting block devices accidentally on failure. Note this commit intentionally does not prevent you from writing qcow2 to a block device. RHV uses this so it is a thing that people do. --- docs/virt-v2v.pod | 32 +++++++++++++++++++++++++++++ v2v/v2v.ml | 51 +++++++++++...

...> inherit output > > @@ -60,8 +50,12 @@ object > method supported_firmware = [ TargetBIOS; TargetUEFI ] > > method prepare_targets _ overlays _ = > - (* Write targets to a temporary local file - see above for reason. *) > - List.map (fun (_, ov) -> TargetFile (tmpdir // ov.ov_sd)) overlays > + (* Although glance can slurp in a stream from stdin, unfortunately > + * 'qemu-img convert' cannot write to a stream (although I guess > + * it could be implemented at least for raw). Therefore we have > + * to write to a tempo...

...argets : source -> (string * overlay) list -> target_buses -> guestcaps -> inspect -> target_firmware -> target_file list method disk_create = (open_guestfs ())#disk_create + method disk_copy target compressed = + let filename = + match target.target_file with + | TargetFile filename -> qemu_input_filename filename + | TargetURI uri -> uri in + let cmd = + [ "qemu-img"; "convert" ] @ + (if not (quiet ()) then [ "-p" ] else []) @ + [ "-n"; "-f"; "qcow2"; "-O"; target.targ...

...block device was deleted, the next run overwrote it with a file. > > * It was not documented anywhere how to do it. > > This commit makes the small code change needed to allow virt-v2v to > write to a block device, only for existing outputs which write to > local files (ie. using TargetFile). Also it avoids deleting block > devices accidentally on failure. > > Note this commit intentionally does not prevent you from writing qcow2 > to a block device. RHV uses this so it is a thing that people do. > --- > docs/virt-v2v.pod | 32 +++++++++++++++++++++++++++++ >...

Since this new temporary directory will contain UNIX sockets for communicating with nbdkit, then its path must not be too long. Use the existing directory that libguestfs exposes for this, i.e. sockdir. --- v2v/nbdkit.ml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/v2v/nbdkit.ml b/v2v/nbdkit.ml index 65317f9b..46b20c9d 100644 --- a/v2v/nbdkit.ml +++ b/v2v/nbdkit.ml

...nged, 1 insertion(+), 1 deletion(-) diff --git a/v2v/v2v.ml b/v2v/v2v.ml index 54a2b3998..363699701 100644 --- a/v2v/v2v.ml +++ b/v2v/v2v.ml @@ -744,7 +744,7 @@ and copy_targets cmdline targets input output = let cmd = let filename = match t.target_file with - | TargetFile filename -> "file:" ^ filename + | TargetFile filename -> qemu_input_filename filename | TargetURI uri -> uri in [ Guestfs_config.qemu_img; "convert" ] @ (if not (quiet ()) then [ "-p" ] else []) @ -- 2.16.2

I have a client box that I: rsync -e ssh targetfile loginname@server:~/destfile since rsyncd is not called I dont get output in the logfile from what I can tell from the man the code and all the articles I have read, there is no way to capture the stats on the serverside rsync call short of using --rsync-path and redirecting stderr+stdout to a l...

...; in - rmdir_on_exit t; - t in object inherit output @@ -60,8 +50,12 @@ object method supported_firmware = [ TargetBIOS; TargetUEFI ] method prepare_targets _ overlays _ = - (* Write targets to a temporary local file - see above for reason. *) - List.map (fun (_, ov) -> TargetFile (tmpdir // ov.ov_sd)) overlays + (* Although glance can slurp in a stream from stdin, unfortunately + * 'qemu-img convert' cannot write to a stream (although I guess + * it could be implemented at least for raw). Therefore we have + * to write to a temporary file. XXX +...

On Tue, 4 Aug 2020, raf wrote: > In such cases, this vulnerability can be mitigated by > the use of an ssh-specific command whitelisting control > such as: Probably just as easy: give the user a restricted shell (/bin/rmksh) as shell and set their PATH etc. suitably, to not include any other commands. bye, //mirabilos PS: Full disclosure: I?m the mksh developer -- ?MyISAM tables

...d headermanipulation of mails. Here an example: 0 * ^From.*gmx.de | (formail -t -I"procmail: gmx.de") >> /var/spool/mail/xxxxxx So, i can add some different headerlines for later evaluation and the result is attached to inbox. Now i have the problem that i don't know name of targetfile, cause it is unique for every mail if maildir is used. I did not found a Option or other workaround to solve this case. I know, it is not a dovecot problem but i hope somebody can give a hint. Could it be a possibility to leave all unchanged? Mails could be transported to /var/spool/mail/xxxxxx a...

...for block devices but other formats such as > qcow2 can be useful in some cases. Sure, I will adjust this. I knew that RHV was using it. > > @@ -713,27 +716,33 @@ and copy_targets cmdline targets input output = > > > > (match t.target_file with > > | TargetFile filename -> > > - (* It turns out that libguestfs's disk creation code is > > - * considerably more flexible and easier to use than > > - * qemu-img, so create the disk explicitly using libguestfs > > - * then pass the 'qemu...

...+ b/v2v/output_glance.ml @@ -59,7 +59,7 @@ object method supported_firmware = [ TargetBIOS; TargetUEFI ] - method prepare_targets _ overlays = + method prepare_targets _ overlays _ = (* Write targets to a temporary local file - see above for reason. *) List.map (fun (_, ov) -> TargetFile (tmpdir // ov.ov_sd)) overlays diff --git a/v2v/output_json.ml b/v2v/output_json.ml index 29c4a1d0..b23420a7 100644 --- a/v2v/output_json.ml +++ b/v2v/output_json.ml @@ -71,7 +71,7 @@ class output_json dir json_options = object method as_options = sprintf "-o json -os %s" dir -...

...; > bye, > > //mirabilos > > PS: Full disclosure: I?m the mksh developer > > I've thought of a valid use for this kind of behaviour > that someone might actually be relying on. :-) > > scp sourcefile remoteserver:'`[ -d /a/b/c ] || mkdir -p > /a/b/c`/a/b/c/targetfile' > > (i.e. ensure that the destination directory exists before writing the file > to it) > > cheers, > raf > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/...

Fixes some of the more egregious problems with v1, and also applies properly to the head of git without needing any other patches. Rich.

...as > > qcow2 can be useful in some cases. > > Sure, I will adjust this. I knew that RHV was using it. > > > > @@ -713,27 +716,33 @@ and copy_targets cmdline targets input output = > > > > > > (match t.target_file with > > > | TargetFile filename -> > > > - (* It turns out that libguestfs's disk creation code is > > > - * considerably more flexible and easier to use than > > > - * qemu-img, so create the disk explicitly using libguestfs > > > - * the...

...let disk_id = create_one_disk run_python tmpdir conn output_password + output_format output_alloc + output_storage source t in + + (* XXX Temporarily spool disks to tmpdir. *) + let target_file = TargetFile (tmpdir // t.target_overlay.ov_sd) in + { t with target_file }, disk_id + ) targets in + target_disk_ids <- List.map snd targets; + List.map fst targets + + method create_metadata source targets _ guestcaps inspect target_firmware = + (* Upload the spooled disks. *) +...

This adds --print-target. In addition, v2 provides a machine-readable version (in JSON format). All of the record -> JSON boilerplate in this patch could be eliminated if we moved the baseline to OCaml 4.02. Rich.