similar to: test

Hi, I'm looking over the Wine documentation, and it says that the particular version that looks like it will work with my version of RedHat 7.1 will only work if the glibcc is 2.2 or above. How do I tell? I"m a newbie and not sure exactly what the glibcc is. TIA

Hi, I'm trying to install the game "Aquanox" under Wine which needs DirectX 8.0. I've found a mail in the wine mailing list archive stating that wine already includes DirectX, but Aquanox keeps complaining about a missing d3d8.dll. Trying to install DirectX 8.0, I end up with "DirectX couldn't be installed on this computer". Any hints on this one? Sebastian --

Real Server is *not* an free product! It takes more than 500 Euro for a 50 Connections a time / Licence. Stefan Jacobi <p>----- Original Message ----- From: "Rob Burris" <robeb@keepthevibe.com> To: <icecast@xiph.org> Sent: Sunday, July 07, 2002 5:42 AM Subject: Re: [icecast] Icecast is cool, but how about video? <p>> *This message was transferred with a

rsync v3.1.0 linux v4.4.104-39-default x86_64 Found in the system log: 2018-02-22T05:02:00-0700 sma-server3 python3[31371]: backintime (sma-user3x/3): WARNING: Command "rsync -rtDHh --links --no-p --no-g --no-o --info=progress2 --no-i-r --delete --delete-excluded -i --dry-run --out-format="BACKINTIME: %i %n%L" --chmod=Du+wx --exclude="/bkp/cgate-backintime"

Just to understand what you'd call "free": Is the client that you use free as well? =) Imho not, and it's quite annoying to see this trial-reminder... On Sun, 2002-07-07 at 07:30, Rob Burris wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > http://licensekey.realnetworks.com/rnforms/products/servers/eval/?ulf=bas > > it's free

*This message was transferred with a trial version of CommuniGate(tm) Pro* Will asterisk actually convert between two different codecs????? ie, a SIP endpoint running GSM and another running G.711? Wouldn't that add quite some latency? I was always under the impression Asterisk did not recompress and was smart enough to negotiate the right codec at each end and just pass through the RTP

incominglimit is already implemented for SIP. Just specify under the endpoint how many incoming connections are allowed. For example, [cisco] type=friend username=cisco secret=blah nat=yes ; This phone may be natted host=dynamic canreinvite=no ; Cisco poops on reinvite sometimes qualify=200 ; Qualify peer is no more than 200ms away

I have installed samba on two different linux boxes that have identical os one system has only win95 and wfwg. All works perfect second system has only NT4.0 I can attach and use the 'public' guest ok= yes shares just fine the 'homes' shares and printers are visible. when I try to attach to a homes share of userxx by machine name userxx I get the same old 'access

*This message was transferred with a trial version of CommuniGate(r) Pro* Greetings, aLL. There's samba-3.0.23d, running on FreeBSD-5.3 as Win2000 AD domain member. For logging user activity on share VFS module full_audit is used (with help of syslog). Logging works well, but some errors appears in log, especially when changing ACLs on share file objects from win-clients: === Nov 30

We're trying some migration tests ... from CommuniGate to Dovecot. The migration program does an APPEND into the new mailbox: src>: a0 FETCH 2900 (FLAGS INTERNALDATE RFC822.PEEK) src<: * 2900 FETCH (FLAGS (\Seen) INTERNALDATE "29-Aug-2005 18:36:54 +0000" RFC822 {1194157} src<: ) dst>: bAPP APPEND "INBOX" (\Seen) "29-Aug-2005 18:36:54 +0000" {1194157}

*This message was transferred with a trial version of CommuniGate(tm) Pro* I've browsed the list but I haven't seen an issue like this one: We have 3 Linux boxes with Samba shares. 2 of them are SuSE 9.0 Professional with Samba 2.2.8, and one has SuSE Open Enterprise Server 9 with Samba 3.x. These are setup as a workgroup, not a domain. The two 2.2.8 boxes have shares that allow guest

Hi, It would be very useful to have a parameter(s) that allows a list of IP addresses, for which verbose debugging takes place. This would be extremely helpful for tracking odd cases that do not occur consistently, and for troubleshooting machine-specific issues. example smb.conf entries: debug ip list level = 10 debug ip list = 192.168.0.151 192.168.0.136 Ideally this would be available

*This message was transferred with a trial version of CommuniGate(tm) Pro* In setting up Asterisk, I'm looking to dump my current phone system (Nortel Venture). I presently have three POTS lines. I would use a VOIP provider, but now are presently available in the Toronto, ON, CANADA area that support user owned hardware/software. I need a 416/647 area code number. In looking at FXO cards

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

Hi! I am distributing 2.5.1p1 for production use on my system by now and prepare switching to protocol 2 as default protocol. I just noted, that ssh-agent can be used for protocol 1 and 2, but the keys kept in ssh-agent are not compared against keys in .ssh. Example: I have a DSA key in id_dsa which I load into ssh-agent on login. When connecting to an account accepting the key everything is

Hi all! I have a problem with CentOS 4.4 and Communigate Pro 5.0.9. As our user number grows, we are seeing "too many files open" error messages in Communigate logs. I spoke with Communigate tech support and they asked me to increase the number of file descriptors which i did. I put 128000 as a script i made to check Communigate open files reported as high as 99000.

Howdy, After upgrading to 2.9 (OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f) I'm unable to ssh between two systems any more (the two that I've upgraded). I've recompiled from the original source several times, each time with no errors, regenerated host keys, regenerated client keys (using rsa), etc., to no avail. Below are some relevant snippets of debugging output

No response yet, so resending. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords ---------- Forwarded message ---------- Date: Fri, 12 Oct 2001 09:44:54 +0300 (EEST) From: Pekka Savola <pekkas at netcore.fi> To: Damien Miller

On Wed, Sep 13, 2000 at 09:13:26AM +0000, Graham Murray wrote: > On upgrading to openssl 0.9.6-beta1, I find that openssh 2.2.0p1 fails > to connect. I did some more experiments and also saw the problems. They occur when using a 0.9.6-beta client to connect to 0.9.5a and 0.9.6-beta servers. They also occur when using a 0.9.5a client connecting to a 0.9.6-beta server. Connections fail with

Hi! as I just noted, after scp the connection does not shut down properly. When I do a "scp file targethost:path", on targethost a "sshd" process is left running. I do use --with-default-path="/usr/local/openssh/bin:/usr/bin:/usr/local/bin" to assure, that the corrensponding openssh-scp is used. It also seems, that normal sessions are not always closed properly.