Displaying 5 results from an estimated 5 matches for "cavi".
Did you mean:
avi
1999 Nov 06
2
Win98 SE, Samba 2.0.5, abysmal write performance
I am running Win 98 SE and have a Samba server v2.0.5 on a FreeBSD 3.3
system. Both machines sit on the same 100baseTX subnet. I am seeing
expected read performance, but writes from Win98 to the Samba share are
terrible; upwards of 30 seconds to copy a 900kb file (yes, that's kb).
This happens in both Explorer, the DOS "shell", and in the application that
actually created the file
2000 Feb 10
0
Errors from remote_password_change()
Greetings,
This may be a bit skewed from the normal discussion here.
I am attempting to use the remote_password_change() function from
passchange.o (a libsmb.a sure would be a nice addition to the samba
distribution...) in a standalone application. I note that, when called out
of smbpasswd, I can change a password on a remote NT server just fine.
When run from a standalone app, however, the
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