search for: systemy

Displaying 15 results from an estimated 15 matches for "systemy".

Did you mean: system
2004 Dec 06
0
Useful information - UK exchanges and SystemX/SystemY and how ISDN works!
Hi all, I thought this may be useful information for the Brits reading this list: I installed a * box (one ZapHFC BRI) for a customer last week and noticed the following warning every fifty seconds: == Primary D-Channel on span 1 down Dec 6 17:31:19 WARNING[213005]: chan_zap.c:1989 pri_find_dchan: No D-channels available! Using Primary on channel anyway 3! == Primary D-Channel on span 1
2010 Jun 05
0
When im login the error: "A device attached to the systemis not functioning"
SNIP > > I've got a Samba server running with an Open LDAP backend in Centos > 5.5, I > could not login with the Administrator's account in window xp clients, > > When im login the error is come: "A device attached to the system is > not > functioning" The only time I've seen that Windows error is during machine joins. It is due to nssldap
2010 Nov 07
3
Issues with Rainbow 6 Vegas
I can start Rainbow 6 Vegas, but after a few minutes of playing it crashes. I have tried it with and without winetricks d3dx9. I am on a macbook pro (NVidia 9600GT, 4gb Ram, 2.66 GHz Intel Core 2 Duo). The OS is 10.6.4 (with the graphic update). I have tried both x11 and xquartz. The terminal spits out this while the game is running: http://pastebin.com/NCiEh5Q1 Thanks
2003 Jun 03
0
virus znaleziony w wyslanej wiadomosci / found in sent message "Re: 45443-343556"
Uwaga / Attention: samba@samba.org W wiadomosci ktora wyslales/as zostal znaleziony virus. Ten program antywirusowy przechwycil i zatrzymal cala wiadomosc zanim dotarla do odbiorcy. A virus was found in an Email message you sent. This Email scanner intercepted it and stopped the entire message reaching it's destination. virus zostal zidentyfikowany jako: The virus was reported to be:
2002 Jun 21
2
Rshaper Weirdness
Hello, guys, I am trying to get rshaper 2.01 to work on our Redhat 6.2 servers, but it does not seem to be able to control the bandwidth usage, here are the details, 1. Our production servers are all Redhat 6.2 with Kernel 2.2.19-6.2.12, the software we use are customized specifically for RH6.2, so I can''t upgrade to 2.4 kernel. 2. On my test server with the same RH6.2 and kernel (it has
2005 Nov 21
2
[Hardware] Good Server I/O on-the-cheap: ASL Monarch 811x with CentOS 4.2 ...
Since good server designs have come up in the past, I wanted to point out a "low-cost" server option that has good I/O, and the vendor offers _your_choice_ of not only Fedora Core or Red Hat Enterprise Linux, but _also_ CentOS _shipped_ with it! IN-A-NUTSHELL ... Starting at just over $750, you can get a single Socket-939 Opteron 1xx (dual-core is an option) system with up to 4GiB of
2003 Sep 08
0
Your command, Re: Your application, was invalid
...usi obsahovat alespon dva znaky LAST n [3] Ziskani novych a zmenenych klicu za poslednich n dni ------------------------------------------------------------------------------- [1] OCEKAVEJTE OBSAHLE ODPOVEDI Tyto prikazy vraci enormne velke mnozstvi informaci, budte proto opatrni! Nektere systemy nemusi zvladnout zpravy takove velikosti a v techto pripadech budou zpravy vraceny na server klicu. Dostanete take pravdepodobne mnohem vice klicu, nez budete kdy potrebovat. Zde jsou velikosti souboru aktualni ke dni 28.2.1997, muzete vsak ocekavat, ze budou rychle narustat: -...
2003 Sep 08
0
Your command, Re: Your application, was invalid
...usi obsahovat alespon dva znaky LAST n [3] Ziskani novych a zmenenych klicu za poslednich n dni ------------------------------------------------------------------------------- [1] OCEKAVEJTE OBSAHLE ODPOVEDI Tyto prikazy vraci enormne velke mnozstvi informaci, budte proto opatrni! Nektere systemy nemusi zvladnout zpravy takove velikosti a v techto pripadech budou zpravy vraceny na server klicu. Dostanete take pravdepodobne mnohem vice klicu, nez budete kdy potrebovat. Zde jsou velikosti souboru aktualni ke dni 28.2.1997, muzete vsak ocekavat, ze budou rychle narustat: -...
2003 Sep 08
0
Your command, Re: Your application, was invalid
...usi obsahovat alespon dva znaky LAST n [3] Ziskani novych a zmenenych klicu za poslednich n dni ------------------------------------------------------------------------------- [1] OCEKAVEJTE OBSAHLE ODPOVEDI Tyto prikazy vraci enormne velke mnozstvi informaci, budte proto opatrni! Nektere systemy nemusi zvladnout zpravy takove velikosti a v techto pripadech budou zpravy vraceny na server klicu. Dostanete take pravdepodobne mnohem vice klicu, nez budete kdy potrebovat. Zde jsou velikosti souboru aktualni ke dni 28.2.1997, muzete vsak ocekavat, ze budou rychle narustat: -...
2003 Aug 21
0
Your command, Re: Re: My details, was invalid
...usi obsahovat alespon dva znaky LAST n [3] Ziskani novych a zmenenych klicu za poslednich n dni ------------------------------------------------------------------------------- [1] OCEKAVEJTE OBSAHLE ODPOVEDI Tyto prikazy vraci enormne velke mnozstvi informaci, budte proto opatrni! Nektere systemy nemusi zvladnout zpravy takove velikosti a v techto pripadech budou zpravy vraceny na server klicu. Dostanete take pravdepodobne mnohem vice klicu, nez budete kdy potrebovat. Zde jsou velikosti souboru aktualni ke dni 28.2.1997, muzete vsak ocekavat, ze budou rychle narustat: -...
2011 Oct 28
3
[LLVMdev] [cfe-dev] RFC: Upcoming Build System Changes
...could > experiment with systems like Ninja which expect to be targetted by a > generator of some kind. > > > Proposal > -------- > > My initial proposal is focused at moving us to use explicit library > dependencies, but paves the way for centralizing more "build systemy" stuff > in > the future. > > * Every LLVM "component" (roughly corresponds to each place we have a > Makefile > or CMakeLists.txt currently) will get a 'LLVMBuild.txt' file. > > This file will be an LLVM specific description of that component. &g...
2011 Oct 28
19
[LLVMdev] RFC: Upcoming Build System Changes
...rate good Makefiles for our project, or could experiment with systems like Ninja which expect to be targetted by a generator of some kind. Proposal -------- My initial proposal is focused at moving us to use explicit library dependencies, but paves the way for centralizing more "build systemy" stuff in the future. * Every LLVM "component" (roughly corresponds to each place we have a Makefile or CMakeLists.txt currently) will get a 'LLVMBuild.txt' file. This file will be an LLVM specific description of that component. Initially, it will look something l...
2011 Oct 28
0
[LLVMdev] [cfe-dev] RFC: Upcoming Build System Changes
...nerate good Makefiles for our project, or could experiment with systems like Ninja which expect to be targetted by a generator of some kind. Proposal -------- My initial proposal is focused at moving us to use explicit library dependencies, but paves the way for centralizing more "build systemy" stuff in the future. * Every LLVM "component" (roughly corresponds to each place we have a Makefile or CMakeLists.txt currently) will get a 'LLVMBuild.txt' file. This file will be an LLVM specific description of that component. Initially, it will look something like...
2011 Oct 28
0
[LLVMdev] [cfe-dev] RFC: Upcoming Build System Changes
...ld > experiment with systems like Ninja which expect to be targetted by a > generator of some kind. > > > Proposal > -------- > > My initial proposal is focused at moving us to use explicit library > dependencies, but paves the way for centralizing more "build systemy" stuff in > the future. > > * Every LLVM "component" (roughly corresponds to each place we have a Makefile > or CMakeLists.txt currently) will get a 'LLVMBuild.txt' file. > > This file will be an LLVM specific description of that component. Initially,...
2011 Nov 01
0
[LLVMdev] RFC: Upcoming Build System Changes
...d > experiment with systems like Ninja which expect to be targetted by a > generator of some kind. > > > Proposal > -------- > > My initial proposal is focused at moving us to use explicit library > dependencies, but paves the way for centralizing more "build systemy" stuff in > the future. > > * Every LLVM "component" (roughly corresponds to each place we have a Makefile > or CMakeLists.txt currently) will get a 'LLVMBuild.txt' file. > > This file will be an LLVM specific description of that component. Initial...