search for: jabberwocky

Hello, I have a problem with 'grep' I read several lines from a file p <- readLines(pfile,n=8) now I have to check that a key word "JABBERWOCKY" is not in that segment a <- grep("JABBERWOCKY",p) which gives a 1 if the key is in the text or 'numeric(0) how can I test it if(a==1) gives Ok in one case and error:missing value where logical needed in the other. How can I coerce 'a' to be 0 or 1? thanks for any hel...

Hi, I am trying to figure out an approach to load in our initial data into our database. I have written some load_data migrations which populate a lot of the stuff, how some of the database items are images etc and I am trying to figure out how to approach added them to the database during a rake db:migrate I am thinking if I store the files in a folder off the RAILS_ROOT I should be able to

...s the result of a "typo" on the part of logrotate -- and who ever heard of machines making typos! root at beauregard logrotate.d]# cat sa-update /var/log/sa-update.log { monthly notifempty missingok } [root at beau Perhaps the Menehune, speaking Jabberwocky? :-) At any rate, there are 16 files in /etc/logrotate.d containing a "notifempty" line and it hiccuped only the one time.

I have a samba 2.2.8a PDC, no windows servers at all. The local network works. Conan, the PDC also acts as a WINS server. Postie, the DHCP server sets: option netbios-name-servers 192.168.1.241 ; option netbios-node-type 2 ; All clients have lmhosts file with: 192.168.1.241 conan #pre #dom:sjsa 192.168.1.242 postie #pre Last week I needed to reinstall a computer, named pixel On server

Hello, I understand the need for a proper stride setting when formatting a filesystem on a RAID device. However, is there any problem in using a stride setting when formatting a filesystem on a regular non-RAID, non-SSD, just plain-vanilla-single-disk block device? I'm sure there isn't any benefit to it, but I'm curious if there is any harm. The reason I ask is I'm looking at

...SHADOW. Unable to sync browse lists in this workgroup. : 96 Time(s) Here's the output of my smb.conf file; #======================= Global Settings ===================================== [global] # workgroup = NT-Domain-Name or Workgroup-Name workgroup = shadow netbios name = Jabberwocky # server string is the equivalent of the NT Description field server string = Jason's Server # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks an...

I'm currently working with a testing system that involves running mkfs.ext3 on some pretty large devices on a regular basis. This is getting fairly painful, and I was wondering if there was some way to speed this up. Understood that the end result might be a filesystem that has less of a safety factor (say, fewer superblock backups) but the tradeoff might be worth it in this case. David

I have an odd problem that involves clients deleting files they should not be able to delete, and claiming success, but then the files "come back" again. Here's the setup: I have a filesystem that contains a file "foobar.txt" owned by user "test", group "test". Permissions on this file are 644, permissions on the enclosing directory are 777. I share

I am trying to export a Fuse filesystem filesystem via Samba (Samba 3.0.7, latest CVS Fuse on kernel 2.6.10). Fuse (http://fuse.sourceforge.net) is a library and kernel module to allow writing filesystems in userspace. I'm having a problem, however, in one odd place. Basically, the export works, and files are readable. However, when putting a new file in via drag-and-drop, windows (XP)

Hello, I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: menuentry 'boot ISO image' { linux16 /memdisk iso initrd16 /my-image.iso.gz } When selected, this starts to boot and then fails with: Ramdisk at 0x37979000, length 0x0033b298 gzip image: decompressed addr 0x7f7f7000, len

I have seen this happen a number of times: Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 kernel: Aborting journal on device sda5. Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 last message repeated 6 times Jun 13 13:58:18 n202 kernel: ext3_abort