Re: [zfs-discuss] How to safely parse "zpool get all" output?

2010-12-06 Thread Richard Elling
Spaces are permitted in the value field. We (myself and Nexenta) use them extensively. -- richard On Dec 6, 2010, at 1:40 PM, Peter Taps wrote: > Folks, > > Command "zpool get all poolName" does not provide any option to generate > parsable output. The returned output contains 4 fields - nam

Re: [zfs-discuss] How to safely parse "zpool get all" output?

2010-12-06 Thread Peter Taps
Hi, Thank you for your help. I actually had the script working. However, I just wanted to make sure that spaces are not permitted within the field value itself. Otherwise, the regular expression would break. Regards, Peter -- This message posted from opensolaris.org __

Re: [zfs-discuss] How to safely parse "zpool get all" output?

2010-12-06 Thread Roy Sigurd Karlsbakk
> Command "zpool get all poolName" does not provide any option to > generate parsable output. The returned output contains 4 fields - > name, property, value and source. These fields seems to be separated > by spaces. I am wondering if it is safe to assume that there are no > spaces in the field va

Re: [zfs-discuss] How to safely parse "zpool get all" output?

2010-12-06 Thread Roy Sigurd Karlsbakk
> Command "zpool get all poolName" does not provide any option to > generate parsable output. The returned output contains 4 fields - > name, property, value and source. These fields seems to be separated > by spaces. I am wondering if it is safe to assume that there are no > spaces in the field va

[zfs-discuss] How to safely parse "zpool get all" output?

2010-12-06 Thread Peter Taps
Folks, Command "zpool get all poolName" does not provide any option to generate parsable output. The returned output contains 4 fields - name, property, value and source. These fields seems to be separated by spaces. I am wondering if it is safe to assume that there are no spaces in the field v