search for: cported

>>>>> "Stephen" == Stephen Arthur <sarthur67 at yahoo.com> writes: Stephen> The SAS data set I PROC CPORTed is [9] the result is [10]. Stephen> I PROC CIMPORTed [10] back to its orginal state [9], and it Stephen> worked. Stephen> So the SAS people think that the error is not with the SAS Stephen> XPORT file, but with R trying to load a text SAS XPORT Stephen> file, when it shoul...

Dear Rxperts! My colleagues used SAS PROC COPY to generate the xpt files that could be read by the available "xpt" file reading packages in R. However, I am unable to use the R packages for reading SAS transport files generated through SAS PROC CPORT. I have tried SASxport, Hmisc, and foreign. Any ideas/suggestions are more than welcome! Thanks so much! Santosh [[alternative HTML

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer

Hello I am sure this is elementary, but I can't figure it out..... I am using SAS v8.2 and R 1.4.1 on a Windows platform. I have a large (6 megabyte) file in .sd2 format. I want to import it into R. If necessary, I can create a smaller file, as I don't need all the variables that are in this file I downloaded the package foreign. I then tried to use PROC CPORT in SAS to create a

Hi, I am trying to read a SAS version 9.1.3 SAS dataset into R (to preserve the SAS labels), but am unable to do so (I have read in a CSV version). I first created a transport file using the SAS code: libname ces2 'D:\CES Analysis\Data'; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc

Hi all, I''m trying to make a simple mapping application that shows to a given point (city, zip etc.) the appropriate map from Google. This is done by updating a div tag via link_to_remote with the Google map code (lot of JavaScript code; see example http://www.google.com/apis/maps/documentation/) Clicking on the ajax''ed link let crash Firefox immediately whereas IE seems

Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with

Hello, everyone! I would like to solve the following problem. Btw, I''m terribly sorry about the pseudo-asciiart, but that''s all I can paint as a tropology. I''m hoping it''ll be enough. ----Internet---- | | | eth0 machine A routing+ipchains eth1 | ------------------ machine B So, given I''m running kernel 2.4.19 and using ipchains

I have encountered a problem reading SAS transport files on both a Mac (OS X) and Linux (RedHat 9), both using R2.0.1. After loading "foreign", the command: read.xport("V1622101_050304.xpt") yields: Error in lookup.xport(file) : File not in SAS transfer format In Linux, I can "cat" the file. The first few lines are: **COMPRESSED** **COMPRESSED** **COMPRESSED**

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

Hello, i've found a strange bug, here is my situation: - all of our computers makes a pxeboot request by default dhcp server is configured: option option-128 code 128 = string; option option-129 code 129 = text; option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned

Hi: First - pxelinux works great - got it up and running with few problems. However - I ran into a snag, I am assuming I have a configuration issue. Here are the details. Using: syslinux-1.75 dhcp-3.0pl1 tftp-hpa-0.29 A lot of what I have done is from: http://frank.harvard.edu/~coldwell/diskless dhcpd.conf: # DHCP configuration file for DHCP ISC 3.0 ddns-update-style

Hello. In my case I can successfully boot up my Thinkpad X32, but the same configuration doesn't work for my desktop computer with Intel network card, with Intel Boot Agent 2.2 DHCP server is 10.0.0.1, tftpd (used tftp-hpa) runs on 10.0.0.32. netstat told me the daemon listen to 69 UDP port just fine. running tftp in commandline also shows it works (retrieve pxelinux.0 less then 1 second).

Sorry for top-posting but my webmail forces me to. I added -W to the APPEND line as suggested but I'm still getting the same result: Booting... Altiris, inc. X86PC PreBoot, PXE-2.x Enhanced Build ID=402 PXEPreZero: Invalid PXE Server list format. and the client PC freezes right there. Here's the full content of my dhcp.conf: max-lease-time 86400; ddns-update-style interim;

That is what I thought, but just to clarify: I am using static dhcp hosts in the dhcpd.conf and our network config. is similar to this: 3 subnets 192.168.15.0/24 192.168.16.0/24 192.168.17.0/24 dhcpd.conf ### Global Settings for DHCP Services ### option domain-name="dom.com"; default-lease-time 900; max-lease-time 1800; ddns-update-style none; authoritative; allow bootp; allow

Even though the FDA has no policies at all that limit our choices of statistical software, there is one defacto standard in place: reliance of the SAS transport file format for data submission (even though this format is deficient for this purpose, e.g., it does not even document value labels or units of measurement in a self-contained way). Because of the widespread use of SAS transport files in

Hi, We are using PXELinux 1.75, ISC DHCP 3.0pl1 and atftp-0.6 to deploy RH 7.3 across a number of Dell Rackmount systems. I would like to set things up so that the RH boot kernel grabs the IP Address, gateway aand DNS address from the first DHCP request with 'ipappend 1', but so far have had no success, Kickstart issue a seconed request after booting the kernel. Here are my configs:

Scot, Thanks for the additional information. On further reflection... whether one uses SAS PROC EXPORT or uses a SAS LIBNAME yourfile XPORT 'yourpathname'; statement, an intermediate file is created in either case. As far as experience tells me now, PROC EXPORT is a far superior choice, because variable names do not get truncated and you only have to deal with reading in a simple text

On Wed, Mar 5, 2014 at 1:55 AM, Vieri <rentorbuy at yahoo.com> wrote: > Sorry for top-posting but my webmail forces me to. Odd. It's been a while since I used Yahoo but I didn't think I had that issue. GMail does default to top-posting but clicking the ellipsis to look at the previous email is enough. > I added -W to the APPEND line as suggested but I'm still getting

The rule: ACCEPT loc $FW::3128 tcp www doesn''t work propertly, the http access does not redirect to squid but directly exit. what''s wrong? Thanks ------- Dario Lesca (d.lesca@ivrea.osra.it) -------------------------------------- @@@@@@@ this is my shorewall-1.2.13 config: #[/etc/shorewall/common.def]-----------------------------------------------