search for: progress_message

...NAME= TARBALL= LOGFILE= HTMLDIR= BUILDTARBALL= BUILDRPM= BUILDXML= BUILDHTML= BUILDLRP= ################################################################################ # F U N C T I O N S ################################################################################ progress_message() { echo >> $LOGFILE echo "$@" | tee -a $LOGFILE echo >> $LOGFILE } report() { echo "$@" | tee -a $LOGFILE } do_or_die() { eval $@ || { progress_message "Step \"$*\" FAILED" ; exit 2; } } fatal_error(...

...,7 +1168,7 @@ if [ -n "$PROVIDERS" ]; then if [ -n "$DEFAULT_ROUTE" ]; then - run_ip route replace default scope global $DEFAULT_ROUTE + ensure_and_save_command ip route replace default scope global $DEFAULT_ROUTE progress_message " Default route $DEFAULT_ROUTE Added." fi in this patch, the ensure_and_save_command could be swapped with run_and_save_command, depending on the action shorewall should take if this command returns an error. Hope this helps, ________________________ Eduardo Ferreira Ic...

I''ve upgraded a 3-interface system from 2.0.8 to 3.2.6 on Debian, and I''m not able to make DNAT work anymore. If someone could offer a suggestion of where to look to fix this, it would be very much appreciated. Problem Summary: If I set DETECT_DNAT_IPADDRS=Yes, then I can''t access anything on my DMZ via DNAT. If I set DETECT_DNAT_IPADDRS=No, then **EVERYTHING**

I''ve upgraded a 3-interface system from 2.0.8 to 3.2.6 on Debian, and I''m not able to make DNAT work anymore. If someone could offer a suggestion of where to look to fix this, it would be very much appreciated. Problem Summary: If I set DETECT_DNAT_IPADDRS=Yes, then I can''t access anything on my DMZ via DNAT. If I set DETECT_DNAT_IPADDRS=No, then **EVERYTHING**

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled

...ton, MA 02110-1301 USA. > + */ > + > +extern crate guestfs; > + > +use std::str; > +use std::sync::{Arc, Mutex}; > + > +#[test] > +fn log_messages() { > + let close_invoked = Arc::new(Mutex::new(0)); Ditto as in 410_close_event.rs. > diff --git a/rust/tests/430_progress_messages.rs b/rust/tests/430_progress_messages.rs > new file mode 100644 > index 000000000..a1d33aff7 > --- /dev/null > +++ b/rust/tests/430_progress_messages.rs > @@ -0,0 +1,61 @@ > +/* libguestfs Rust bindings > + * Copyright (C) 2019 Hiroyuki Katsura <hiroyuki.katsura.0513@gmail....

...ot;Warning: $host does appear to be in zone $zone already" + else + [ -z "$hosts" ] && hosts=$hostlist || hosts="$hosts $hostlist" + fi fi eval ${z}_hosts=\"$hosts\" @@ -7088,7 +7092,6 @@ fi fi done < ${STATEDIR}/chains - progress_message "$newhost added to zone $zone" done @@ -7184,7 +7187,7 @@ fi done - [ -n "$found" ] || error_message "Warning: $1 does not appear to be in zone $2" + [ -n "$found" ] || error_message "Warning: $host does not appear to be in zone...

...| 8 +- rust/src/event.rs | 158 ++++++++++++++++++++++++++++ rust/src/lib.rs | 2 + rust/tests/040_create_multiple.rs | 2 +- rust/tests/410_close_event.rs | 38 +++++++ rust/tests/420_log_messages.rs | 60 +++++++++++ rust/tests/430_progress_messages.rs | 61 +++++++++++ 9 files changed, 381 insertions(+), 10 deletions(-) create mode 100644 rust/src/event.rs create mode 100644 rust/tests/410_close_event.rs create mode 100644 rust/tests/420_log_messages.rs create mode 100644 rust/tests/430_progress_messages.rs diff --git a/generator/rust....

hello , i''m currently trying to set-up Traffic Shapping with Shorewall and I have strong feelings that I found a bug. I may be mistaken, but I tried everything and can''t get it to work. I''ve turned ON TC_ENABLED=Yes and CLEAR_TC=Yes when i start shorewall ( shorewall start ), i get this message : Setting up Traffic Control Rules... TC Rule "2 eth1 0.0.0.0/0 tcp

...crate guestfs; > > + > > +use std::str; > > +use std::sync::{Arc, Mutex}; > > + > > +#[test] > > +fn log_messages() { > > + let close_invoked = Arc::new(Mutex::new(0)); > > Ditto as in 410_close_event.rs. > > > diff --git a/rust/tests/430_progress_messages.rs b/rust/tests/ > 430_progress_messages.rs > > new file mode 100644 > > index 000000000..a1d33aff7 > > --- /dev/null > > +++ b/rust/tests/430_progress_messages.rs > > @@ -0,0 +1,61 @@ > > +/* libguestfs Rust bindings > > + * Copyright (C) 2019 Hiroyuki...

...ed components above) cant jump to MASQUERADE target. Is there a known solution, workaround etc. related to the problem? Is it a frequent symptom? Or I misconfigured something...? Have a nice day: Balázs NÉMETH, Hungary, Budapest + echo ''Masqueraded Networks and Hosts:'' + save_progress_message ''Restoring Masquerading/SNAT...'' + echo + echo ''progress_message "Restoring Masquerading/SNAT..."'' + echo + read fullinterface networks addresses proto ports ipsec + expandv fullinterface networks addresses proto ports ipsec + local varval + ''[...

...++++++ rust/src/bin/event_leak.rs | 30 ++++++ rust/src/error.rs | 6 ++ rust/src/event.rs | 146 ++++++++++++++++++++++++++++ rust/tests/410_close_event.rs | 39 ++++++++ rust/tests/420_log_messages.rs | 60 ++++++++++++ rust/tests/430_progress_messages.rs | 59 +++++++++++ 8 files changed, 369 insertions(+) delete mode 100644 rust/src/bin/.gitkeep create mode 100644 rust/src/bin/event.rs create mode 100644 rust/src/bin/event_leak.rs create mode 100644 rust/tests/410_close_event.rs create mode 100644 rust/tests/420_log_messages.rs create m...

Hi, it seems not to be possible to add more than one host at once to a zone. So shorewall add br0:eth0:192.168.2.10,eth0:192.168.2.11 work fails, since "br0:eth0:192.168.2.10,eth0" is interpreted as one interface. --snip -- iptables v1.2.9: interface name `eth0:192.168.2.10,eth0'' must be shorter than IFNAMSIZ (15) Try `iptables -h'' or ''iptables

This is an updated and extended version of the original patch: https://www.redhat.com/archives/libguestfs/2010-August/msg00163.html This adds OCaml and Perl bindings (both tested), support for progress bars in virt-resize, and adds progress notifications to a number of the simpler commands. Still to do is to add progress messages to more commands. There are still a few commands which would be

...rectory in ''$CONFIG_PATH'' ++ ''['' -f /etc/shorewall/params '']'' ++ echo /etc/shorewall/params ++ IFS='' '' ++ return + local user_exit=/etc/shorewall/params + ''['' -f /etc/shorewall/params '']'' + progress_message ''Processing /etc/shorewall/params ...'' + ''['' -n '''' '']'' + echo ''Processing /etc/shorewall/params ...'' Processing /etc/shorewall/params ... + . /etc/shorewall/params ++ find_file shorewall.conf ++ local saveifs=...

...if not, write to the Free Software + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + *) + +type comment_style = + CStyle | CPlusPlusStyle | HashStyle | OCamlStyle | HaskellStyle + | ErlangStyle | LuaStyle | PODStyle +type license = GPLv2plus | LGPLv2plus + +val progress_message : string + +val protocol_limit_warning : string + +val deprecation_notice : ?prefix:string -> ?replace_underscores:bool -> Types.action -> string option + +val version_added : Types.action -> string option + +val copyright_years : string + +val generate_header : ?extra_inputs:string lis...

This map was originally included just for the java bindings, but is generally useful to any binding which uses camel case by requirement or convention. --- generator/generator_haskell.ml | 4 ++-- generator/generator_java.ml | 10 +++++----- generator/generator_main.ml | 2 +- generator/generator_structs.ml | 12 +++++------- generator/generator_structs.mli | 8 ++++---- 5

Use interfaces files (*.mli files) instead of exporting all symbols randomly. Change the 'file is generated' warnings at the top of generated files so they accurately describe which source file generates each output file. Rich.

This rather complex set of patches allow non-optargs functions to gain optional arguments, while preserving source and binary backwards compatibility. The problem is that we cannot add an optional argument to an existing function. For example, we might want to add flags to the 'lvresize' API which currently has no optional arguments.

libguestfs has used double and triple underscores in identifiers. These aren't valid for global names in C++. (http://stackoverflow.com/a/228797) These large but completely mechanical patches change the illegal identifiers to legal ones. Rich.