f



Re: ods/pdf startpage=never doesn't work anymore in v92? #4

I have used ODS Layout as described in that paper and it is indeed very
nice.

HOWEVER, be forewarned that what is described there may not work in 9.2. I
created (what I thought) was a simple layout where the page was divided into
four equally sized regions (top left, top right, bottom left, bottom right)
where I positioned graphs in the top right and bottom left, and proc reports
in the other two quadrants. I did that in 9.1.3. When I tested it in 9.2 the
graphs were not positioned even close to where they should have been.

I reported the problem to SAS TS in December and they still have not been
able come up with a solution. And please note that this is not a criticism
of TS. ODS Layout was experimental when that paper was written and it is
still experimental in 9.1.3 and 9.2. I understand that it is scheduled for
production in 9.3.

So if you are going to do anything with it, I would encourage you to use 9.2
instead of 9.1.3.

Regards,
-donh

-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Akshaya
Nathilvar
Sent: Thursday, January 29, 2009 2:56 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: ods/pdf startpage=never doesn't work anymore in v92?

Utilize the ODS Layout feature to get the desired text, graphics all in one
page. You can refer to this SUGI
paper<http://www2.sas.com/proceedings/sugi28/148-28.pdf>
 .

Code:

ods listing close;
ods pdf file="abc.pdf" notoc style=minimal startpage=never; ods layout
start;

proc print data=sashelp.class;
run;

goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in
vsize= 2in;

proc gplot data=sashelp.class;
plot weight*height;
run;
quit;
ods layout end;

ods pdf close;
ods listing;

AkshayA!

On Thu, Jan 29, 2009 at 2:36 PM, Ya Huang <ya.huang@amylin.com> wrote:

> Hi there,
>
> The following code when runs on v8.2 will generate a one-page report
> with a table on top and a figure on the bottom. But a two-page report
> with first page as the table and second page as the figure if runs on
> v92, which basically means the startpage=never dosen't work anymore. I
> have a routine report based on the startpage=never, this change
> totally mess up my report!
>
> Is there a way to force v92 to behave as v82 for this matter?
>
> Thanks
>
> Ya
>
> ods listing close;
> ods pdf file="c:\temp\v9junk.pdf" notoc style=minimal; ods pdf
> startpage=never;
>
> proc print data=sashelp.class;
> run;
>
> goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in
> vsize= 2in;
>
> proc gplot data=sashelp.class;
> plot weight*height;
> run;
> quit;
>
> ods pdf close;
> ods listing;
>
0
2/1/2009 9:03:18 PM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
507 Views

Similar Articles

[PageSpeed] 47

Reply:

Similar Artilces:

Re: ods/pdf startpage=never doesn't work anymore in v92?
Utilize the ODS Layout feature to get the desired text, graphics all in one page. You can refer to this SUGI paper<http://www2.sas.com/proceedings/sugi28/148-28.pdf> . Code: ods listing close; ods pdf file="abc.pdf" notoc style=minimal startpage=never; ods layout start; proc print data=sashelp.class; run; goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; ods layout end; ods pdf close; ods listing; AkshayA! On Thu, Jan 29, 2009 at 2:36 PM, Ya Huang <ya.huang@amylin.com> wrote: > Hi there, > > The following code when runs on v8.2 will generate a one-page report with > a table on top and a figure on the bottom. But a two-page report with > first page as the table and second page as the figure if runs on v92, > which basically means the startpage=never dosen't work anymore. I have a > routine report based on the startpage=never, this change totally mess up my > report! > > Is there a way to force v92 to behave as v82 for this matter? > > Thanks > > Ya > > ods listing close; > ods pdf file="c:\temp\v9junk.pdf" notoc style=minimal; > ods pdf startpage=never; > > proc print data=sashelp.class; > run; > > goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in > vsize= 2in; > > proc gplot data=sashelp.class; > plot weight*height; > run; > quit; ...

Re: ods/pdf startpage=never doesn't work anymore in v92? #2
Ya, I agree with you that some ods pdf functionning has changed but the use of never yes and now has always being not generating evident pageskipping the lessons are, i think 1)yes or now has not the same effect in ods pdf 2)creating first a graph on a pdf page permit the addition of another tabular result which will be added from the head of the page but if you must put many graph on a pdf page follow a reasonnable sequence from top to bottom ====================== yours modified=========== ods listing close; ods pdf file="d:\temp\v9junk.pdf" notoc style=minimal; *ods pdf startpage=no; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; proc print data=sashelp.class; run; ods pdf startpage=now; ods pdf close; ods listing; ================= as showed with later code, the results are varying see the excerpt of the documentation ______ ods listing close; ods pdf file="d:\temp\v92junk.pdf" notoc style=minimal; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; data class;set sashelp.class sashelp.class sashelp.class; run; proc print data=class; run; ods pdf startpage=now; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; goptions ...

Re: ods/pdf startpage=never doesn't work anymore in v92? #3
Hi Andre, I read the doc and noticed the same line: "specifying STARTPAGE= NEVER might cause graphics to overprint" In other word, SAS never committed "NEVER" will behave consistently :-( Too bad, I may have to make many changes to some validated codes. Ya -----Original Message----- From: Andre Wielki [mailto:wielki@ined.fr] Sent: Friday, January 30, 2009 2:35 AM To: Huang, Ya Cc: SAS-L@LISTSERV.UGA.EDU Subject: Re: ods/pdf startpage=never doesn't work anymore in v92? Ya, I agree with you that some ods pdf functionning has changed but the use of never yes and now has always being not generating evident pageskipping the lessons are, i think 1)yes or now has not the same effect in ods pdf 2)creating first a graph on a pdf page permit the addition of another tabular result which will be added from the head of the page but if you must put many graph on a pdf page follow a reasonnable sequence from top to bottom ====================== yours modified=========== ods listing close; ods pdf file="d:\temp\v9junk.pdf" notoc style=minimal; *ods pdf startpage=no; ods pdf startpage=never; goptions reset=all horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; proc print data=sashelp.class; run; ods pdf startpage=now; ods pdf close; ods listing; ================= as showed with later code, the results are varying see the excerpt of the documentation ______ ods listing close; od...

ods/pdf startpage=never doesn't work anymore in v92?
Hi there, The following code when runs on v8.2 will generate a one-page report with a table on top and a figure on the bottom. But a two-page report with first page as the table and second page as the figure if runs on v92, which basically means the startpage=never dosen't work anymore. I have a routine report based on the startpage=never, this change totally mess up my report! Is there a way to force v92 to behave as v82 for this matter? Thanks Ya ods listing close; ods pdf file="c:\temp\v9junk.pdf" notoc style=minimal; ods pdf startpage=never; proc print data=sashelp.class; run; goptions reset=all device=sasprtc horigin=1 in vorigin=1 in hsize=2 in vsize= 2in; proc gplot data=sashelp.class; plot weight*height; run; quit; ods pdf close; ods listing; ...

Re: 'do over' doesn't work #4
Hi Ash, What is the purpose of your code? Looking at the test data it appears you want to replace missing numeric values with the number zero and missing character data with a "Z". Replacing missing numerics with zero seems like a pretty standard thing, and therefore there are a few ways to handle this in SAS. Replacing missing character variables with a character, on the other hand is a bit more difficult. You could either approach it with your array method as such: data have; infile cards missover; input x2 x1 x3 x4 x5$ x6$; cards; 2 . 5 1161 AB�LIEN ANIEL 35 6 3 1336 ALM�RIC 82 1 5 1499 ;run; data array_method; set have; array a_varnum _numeric_; array a_varchar _character_; do over a_varnum; if missing(a_varnum) then a_varnum = 0; end; do over a_varchar; if missing(a_varchar) then a_varchar = 'Z'; end; run; proc print;run; An alternative, on your test data would also be to use a Dorfmanesque peek/poke solution. This will only work for provided all your character variables are a length of 8. The array statements are not required, but it will force the variables to occupy contiguous space which is required here. If anyone can suggest a way to make handling variable length character variables using this technique, I would very interested. data peek_poke; array nums [*] x1-x4; array chars [*] $x5 x6; set have; _n_ = dim(nums)*8; call poke(tranwrd(peekc(addr(x1),_n_),put(.,rb8.), put...

Re: SAS xport to R: doesn't work, at least in Open VMS #4
i just like to use a lightweight db to bridge sas and r, such as a mdb or sqlite. and it works pretty well. i think it is much better than conversion to csv, since the data attributes will be preserved. On 6/27/07, Vlad <vladislav.moltchanov@ktl.fi> wrote: > Hi, everybody, > I am a "long time SAS user" not an R user. I have got a task to > transfer to R some SAS datatsets. Forst I started to pilot xport files > created by SAS. However, for some unknown reason, R doesn't recognize > the xport format created by SAS in Open VMS saying > > > test1= ...

Re: Weird problem with ODS PDF
Problem Note 32003: Text searches return different results in PDF files created by ODS PDF http://support.sas.com/kb/32/003.html The Details section for the note clarifies that "different" means "not correct". ;-) Fortunately, a hot fix is available. Search strategy -- I searched in Samples and SAS Notes for the words ODS, PDF, and search. HTH! Mike Rhoads RhoadsM1@Westat.com -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Jeremy Miles Sent: Friday, February 19, 2010 1:02 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Weird p...

Re: Weird problem with ODS PDF
Mike That is a good idea to add the search strategy keywords to your answer. And, if I have not noticed your (and, maybe, others') doing this, shame on me. Nat -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Mike Rhoads Sent: Friday, February 19, 2010 2:14 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: Weird problem with ODS PDF - searching within PDF doesn't work (SAS 9.2 only?) Problem Note 32003: Text searches return different results in PDF files created by ODS PDF http://support.sas.com/kb/32/003.html The Details section for the n...

Re: 'do over' doesn't work
Ash As I recall, the first SAS arrays were not subscripted and did not use direct array references. The do over statement simply said, go through the variables listed in the array starting with the first and going to the last. The erro messages that you received were telling you that you should not use the brackets on the array names. From my standpoint, the beauty of the do over is that it makes coding simpler and, given my clumsy fingers, anything that reduces my chances of screwing up are a help. However, these days, I would not choose to use a do over expression in code that was going to be used in the future since someone following me would probably not know of the syntax and the Do over has not been documented in years. The following code worked for me. DATA TABLE_BIDON; INPUT X1 X2 X3 X4 X5 $; infile cards missover;** missover added; CARDS; 2 . 5 1161 AB�LIEN 35 6 3 1336 ALM�RIC 82 1 5 1499 ;RUN; DATA TABLE_BIDON ; * no drop statement needed here; SET TABLE_BIDON; ARRAY A_VARNUM _NUMERIC_; ARRAY A_VARCAR _CHARACTER_; DO OVER A_VARNUM; IF A_VARNUM = . THEN A_VARNUM = 0; END; DO OVER A_VARCAR; IF COMPRESS(A_VARCAR) IN (".","") THEN A_VARCAR = "Z"; END; RUN; Nat Wooding Environmental Specialist III Dominion, Environmental Biology 4111 Castlewood Rd Richmond, VA 23234 Phone:804-271-5313, Fax: 804-271-2977 ash007 <R...

Re: 'do over' doesn't work #3
On Sat, 24 Jan 2009 14:25:41 +0000, karma <dorjetarap@GOOGLEMAIL.COM> wrote: >Hi Ash, > >What is the purpose of your code? Looking at the test data it appears >you want to replace missing numeric values with the number zero and >missing character data with a "Z". Replacing missing numerics with >zero seems like a pretty standard thing, and therefore there are a few >ways to handle this in SAS. Yes. See http://www.sascommunity.org/wiki/Generating_Zeroes_in_PROC_TRANSPOSE_Output or http://tinyurl.com/abozdc >Replacing missing character variables with >a character, on the other hand is a bit more difficult. > >You could either approach it with your array method as such: > >data have; > infile cards missover; > input x2 x1 x3 x4 x5$ x6$; > cards; >2 . 5 1161 AB�LIEN ANIEL >35 6 3 1336 ALM�RIC >82 1 5 1499 > ;run; > >data array_method; > set have; > array a_varnum _numeric_; > array a_varchar _character_; > do over a_varnum; > if missing(a_varnum) then a_varnum = 0; > end; > do over a_varchar; > if missing(a_varchar) then a_varchar = 'Z'; > end; > run; >proc print;run; > >An alternative, on your test data would also be to use a Dorfmanesque >peek/poke solution. This will only work for provided all your >character variables are a length of 8. The array statements are not >required, but it will force the...

Re: 'do over' doesn't work #2
Ramsamy, The code that follows will get you into DO OVER. Do not use '*' in the dimension statements. Use the implicit index of _I_ t= o refer to individual elements of the array. DATA TABLE_BIDON; INPUT X1 X2 X3 X4 X5 $; CARDS; 2 . 5 1161 ABELIEN 35 6 3 1336 ALMERIC 82 1 5 1499 . ; RUN; DATA TABLE_BIDON ; SET TABLE_BIDON; ARRAY A_VARNUM _NUMERIC_; ARRAY A_VARCAR _CHARACTER_; DO OVER A_VARNUM; IF A_VARNUM[_i_] =3D . THEN A_VARNUM[_i_] =3D 0; END; DO OVER A_VARCAR; IF COMPRESS(A_VARCAR[_i_]) IN (".","") THEN A_VARCAR[_i_] =3D "Z"; END; RUN; Kind regards, Muthia Kachirayan On Sat, Jan 24, 2009 at 6:40 AM, ash007 <RamsamyAshley@gmail.com> wrote: > hi, > > why my code doesn't work with 'do over'. thanks. > > ash007. > > DATA TABLE_BIDON; > INPUT X1 X2 X3 X4 X5 $; CARDS; > 2 . 5 1161 AB=C9LIEN > 35 6 3 1336 ALM=C9RIC > 82 1 5 1499 > ;RUN; > > DATA TABLE_BIDON (DROP =3D _I); > SET TABLE_BIDON; > ARRAY A_VARNUM[*] _NUMERIC_; ARRAY A_VARCAR[*] _CHARACTER_; > > DO OVER A_VARNUM[*]; > IF A_VARNUM[*] =3D . THEN A_VARNUM[*] =3D 0; > END; > > DO OVER A_VARCAR[*]; > IF COMPRESS(A_VARCAR[*]) IN (".","") THEN A_VARCAR[*] =3D = "Z"; > END; > RUN; > ...

Re: why the array doesn't work #4
On Mon, Mar 16, 2009 at 9:52 PM, Nat Wooding <Nathaniel.Wooding@dom.com> wrote: > Terry > > Try removing the "of" from your mean function. The error message > disappeared when I dropped it. > I found something interesting. In the code that follows, s is 4 while t is 6 - data test; x = 1; y = 2; z = 3; run; data _null_; set test; array a{3} x y z; s = sum(a{1}--a{3}); t = sum(of a{*}); put s t; run; Regards, Anindya ...

Re: Why doesn't the macro variables work? #4
Jan , The period to end a macro variable name which is only needed if you follow a macro var name with text you do not want considered part of a macro vars name when the macro facility tries to resolve the macro var. In the case below the & in &mm serves as an end to the first macro vars name and the beginning of the second macro vars name. Toby Dunn The obscure we see eventually. The completely obvious, it seems, takes longer. ~Edward R. Murrow Think like a man of action, act like a man of thought. ~Henri Louis Bergson Alice came to a fork in the road. "Which road d...

Re: FindRoot with NDSolve inside of it doesn't work #4
One more question. I noticed that I do have to "Clear[f]", otherwise the change is not made. How come? I don't have that problem here: f[x_] := 5 f[x_] := 6 f[x] Thanks again, Sam ________________________________ From: Leonid Shifrin <lshifr@gmail.com> To: Sam Takoy <sam.takoy@yahoo.com>; mathgroup@smc.vnet.net Sent: Wed, July 28, 2010 2:52:56 PM Subject: Re: FindRoot with NDSolve inside of it doesn't work Sam, The difference is that in your last example with exponents the r.h.s of the function does not necessarily involve...

Re: 'just' option doesn't work in proc format ?
Hi, The format of the format needs to be a little different ... Try proc format; invalue yy (just default=20) '1.2' = 0 ; run; The options for the invalue need to be in brackets, otherwise PROC FORMAT will think the first value it has to format is "just1.2". The "default=20" part is required, otherwise the comparisons will be done within the length of the format string (3 in this case for "1.2"). Regards ++ Guido. On 27/09/2007, Ya Huang <ya.huang@amylin.com> wrote: > > Hi there, > > According to SAS Online Doc, 'JUS...

SAS TIP: Using Noprint and Ods output together? Doesn't work!
Have ever used the ODS OUTPUT statement to put output into a SAS dataset and then used the noprint option so that the output does not print in the output window? If so, then you know that this does not work. The SAS dataset is empty! The noprint option prevents output from going to any ODS destination, so you cannot use it. However, if you do not want your output to print in the output window, then there is an alternative. ODS Listing Close; This statement prevents any output from showing in the output window, but still allows the ODS OUTPUT statement to store the results in the SAS dataset. Note: The above statement prevents ALL output from going to the output window until you turn the listing back on. Here's how to turn it back on: ODS Listing; Enjoy! Wendi ************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ...

Re: SAS xport to R: doesn't work, at least in Open VMS #2
>> Hi, everybody, >> I am a "long time SAS user" not an R user. I have got a task to >> transfer to R some SAS datatsets. Forst I started to pilot xport files >> created by SAS. However, for some unknown reason, R doesn't recognize >> the xport format created by SAS in Open VMS saying >> >> > test1= read.xport( "NEW_DSIN.XPT") >> Error in lookup.xport(file) : file not in SAS transfer format >> >> I have created these files using several ways. >> 1. >> >> libname xpt xport "NEW_D...

RE: [tao-bugs] BiDirectional GIOP Tests doesn't work anymore #2
Hi, > >>thanks for the answer. > >>Yes, I know, 'AIX is a platform that is not tested at all for TAO', > >>but we are using TAO since about 4 years on AIX with g++ > >>and Bidirectional GIOP was working all the time. > > > > > > We did a lot of work before the summer for AIX with Visual Age. > > But not for g++ :-) No, the customer uses Visual Age. > > Run the server at debug level 10 and look at the output why > the server > > recreates a new connection? Maybe dns is broken? > > No, dns is not broken, but with debug level 10, TAO is saying for the > callback: > > Transport_Cache_Manager::find_i, no idle transport is available > > That is, he simply couldn't find the existing Connection and then > makes a new connection. Could you post a little bit more of the log, maybe it triggers something? Johnny ...

Re: Length function doesn't work (Data too long for column ... tr #4
Irin, While inserting the format statement in the PROC PRINT may eliminate the Warning messages, it does not get to the issue of why these variable lengths (or previous formats) are longer than you expected. If it is the lengths of the variables that are longer than expected, this can affect performance by carrying more information than needed. I think it would be a good idea to do a PROC CONTENTS on FLU_SINGLE2 to determine the lengths of the fields and any associated formats. Then adjust your code so you aren't carrying excessive data or unnecessary formats. Jack Clark Research Ana...

howto update from 4.10 to 6.1 when cvsup doesn't work anymore?
howto update from 4.10 to 6.1 when cvsup doesn't work anymore? May I use my new 6.1-cdrom in any way? On Tue, 25 Jul 2006 11:33:16 +0200 Tobias Steer <steer@abc-werbetechnik.de> wrote: > howto update from 4.10 to 6.1 when cvsup doesn't work anymore? > May I use my new 6.1-cdrom in any way? Updating from 4.x to 6.x by source is going to be a long and painful operation anyway (you'll need to use an intermediate stop somewhere in 5.x around 5.4 IIRC). The best way would be to make sure your data is backed up properly, install 6.1 as a new install and then restore your data into the new OS. -- C:>WIN | Directable Mirror Arrays The computer obeys and wins. | A better way to focus the sun You lose and Bill collects. | licences available see | http://www.sohara.org/ Tobias Steer schrieb: > howto update from 4.10 to 6.1 when cvsup doesn't work anymore? > May I use my new 6.1-cdrom in any way? There are two possibilities: 1. cvsup to 5.x then upgrade to 6.x 2. Install your system completely from the ground up, as that's the easiest way to use UFS2 instead of UFS. IIRC there are reports, that an upgrade from 4.x (UFS) to [5|6].x (UFS2) went "on the fly" - check the archives to be sure. ;) Philipp ...

Re: Length function doesn't work (Data too long for column ... #4 673785
Irin , Like some one already stated you are setting the length of the variables on one data set but printing another. Since we have no idea how you reated the data set you are printing we also have no idea whether or not variables in this data set will inherit the length from the ORIG data set or if they are respecified in some way. Toby Dunn When everything is coming at you all at once, your in the wrong lane. A truly happy person is someone who can smile and enjoy the scenery on a detour. From: Irin later <irinfigvam@YAHOO.COM> Reply-To: Irin later <irinfigvam@YAHOO.COM&...

Re: Re: SphericalPlot3D doesn't work
David, I'm not sure if this is an old message. But, just in case you still need some help, I tried running your program and found no problems. To make a cylindrical or spherical plot, you first need to execute the following command: <<Graphics`ParametricPlot3D`; This command will load the standard package ParametricPlot3D.m. Then, you will need to execute the following command: SphericalPlot3D[2, {theta, 0, Pi}, {phi, -Pi, Pi}]; This should produce the results you are looking for. If you need a soft copy of the notebook that I created, please let ...

FAQ 5.34 Why can't I use "C:\temp\foo" in DOS paths? Why doesn't `C:\temp\foo.exe` work? #4 555136
This is an excerpt from the latest version perlfaq5.pod, which comes with the standard Perl distribution. These postings aim to reduce the number of repeated questions as well as allow the community to review and update the answers. The latest version of the complete perlfaq is at http://faq.perl.org . -------------------------------------------------------------------- 5.34: Why can't I use "C:\temp\foo" in DOS paths? Why doesn't `C:\temp\foo.exe` work? Whoops! You just put a tab and a formfeed into that filename! Remember that within double quoted strings (&qu...

iproute2 fwmark doesn't work (or iptables --set-mark doesn't)
Hi, I just subscribed this group. Hello everyone! I have a problem with setting up routing. In short, I want to mark certain packets with iptables and then catch these marks with iproute2. However Linux seems to ignore these marks. I have a 3.11.4 kernel with CONFIG_IP_ADVANCED_ROUTER and CONFIG_IP_MULTIPLE_TABLES set. Here's my setup: - eth0: LAN - IP 192.168.0.1, netmask /24 - It connects to the LAN - eth1: WAN - IP 192.168.1.180, netmask /24, gateway 192.168.1.1 - It connects to the Internet - tap0: VPN (created with OpenVPN) - Local IP 172.24.25.4, remote IP (and gateway) 172.24.25.2, netmask /24 I want to pass certain traffic through 192.168.1.1 (eth1) and certain through 172.24.25.2 (tap0) - local traffic as well as routed traffic. Rules will be somewhat complicated (for locally-generated traffic and routed traffic), now just let's assume that I want to mark all packets to go through 192.168.1.1. I have added two new routing tables to /etc/iproute2/rt_tables: #v+ 2 vpn 3 wan #v- I've created two of them, so the main table will not have a default gateway. This way I can avoid errors - if I make a mistake and traffic goes through the main table, it won't get out. Tables are then populated: #v+ ip route flush table main ip route add 192.168.0.0/24 dev eth0 table main ip route add 192.168.1.0/24 dev eth1 table main ip route add 172.24.25.0/24 dev tap0 table main ip route flush table...

Web resources about - Re: ods/pdf startpage=never doesn't work anymore in v92? #4 - comp.soft-sys.sas

Resources last updated: 3/16/2016 12:38:59 PM