search for: cavy

Displaying 5 results from an estimated 5 matches for "cavy".

Did you mean: cave
1999 Nov 06
2
Win98 SE, Samba 2.0.5, abysmal write performance
...o the same Samba server-- having a 10/100 hub that bridges is pretty convenient). The mailing list archives don't seem to offer any clues, unless I'm just searching for the wrong words. Does anybody have any ideas? Cheers, John -- John Mechalas \ carpe cavy! Intel MD6 Engineering Computing \ JF1, 2nd floor, near pole C16 \ (seize the guinea pig!) (503) 264-0658 \
2000 Feb 10
0
Errors from remote_password_change()
...so need smbd (I don't see why I would, but I've been wrong before)? Should I just give up and try something else? WHat I need to do is integrate NT password changing into a UNIX app, so other suggestions are welcome. Cheers, John -- John Mechalas \ carpe cavy! Intel PMD Engineering Computing \ JF1, 2nd floor, near pole C16 \ (seize the guinea pig!) (503) 264-0658 \
2013 Jul 15
1
facter 1.6.18 tarball has a dangerous mac preflight script
The facter 1.6.18 tarball has many issues. First, the ext/osx/createpackage.sh script still uses packagemaker, which is deprecated. And even if it used that, there are a few references to files in the now-deleted conf/osx/ directory. So it''s pretty difficult to create a Mac pkg from this, but after some tweaking of the createpackage.sh script, I managed to do it! I ran the package it
2012 Jul 10
2
Refresh not working with launchd service provider?
Hi, Refresh doesn''t seem to be working with the launched service provider on OS X Lion (10.7.4). I''ve come up with a simple "service" script, plist file and puppet script to apply to demonstrate. The problem. Here''s the shell script which logs an initial starting message and then just loops logging a "Still running…" message.
2006 Jul 18
7
Port scan from Apache?
Hi everyone, today I got an e-mail from a company claiming that my server is doing port scans on their firewall machine. I found that hard to believe so I started checking the box. The company rep told me that the scan was originating at port 80 with destination port 8254 on their machine. I couldn't find any hints as to why that computer was subject to the alleged port scans. Searching