similar to: A little help w/ Debian Samba and XP clients

Baxter, I could be wrong, but I thought /etc/printcap was the config for bsd style printing - not cups. Anyone? -- Christopher Barry Manager of Information Systems InfiniCon Systems http://www.infiniconsys.com -----Original Message----- From: Baxter Shepperson [mailto:baxshep@cox.net] Sent: Friday, March 21, 2003 5:24 PM To: samba@samba.org Subject: [Samba] Redhat 8 printcap I am trying to

Hi list. I'm having problems w/ printing using Samba on Redhat 8. Shared drives work fine yet my CUPS printing doesn't work. I sure appreciate any input. For what it's worth, I couldn't find any printing related errors in /var/log/samba/. I notice that the printcap doesn't have a sub-directory named cups like my old Debian box. Could that be it? Here's my smb.conf

Hi all. In the interest of using a more mainstream business distribution, I changed my faithful file/printserver over to Redhat 8.0 from Debian Testing. Now, my shared directories are working fine but printing is not working. I can browse to the printer using net view or Network Neighborhood in Windows or using smbclient -L in Linux but printing is not working. I've checked

Hi list. I've just got Samba up and running as a fileserver just fine. Now I'm trying to use it as a printserver using CUPS. I can see said printer via Network Neighborhood on XP boxes and add it in Windows but no print jobs complete. No errors in Windows yet no printing start on the printer. Would this be a question of spool permissions? Right now I'm using spool

When I encountered weird messages when trying to mount Samba shares on a Linux box the solution was to make sure I had the location of smbmount and smbmnt in my path. On RedHat 6.2 the path is /usr/sbin. I have not seen your exact error before though. Hope that helps. Message: 12 Date: Wed, 27 Nov 2002 10:29:46 -0800 From: Baxter Shepperson <baxshep@cox.net> To: samba@lists.samba.org

OK, I've tried changing my printcap name from printcap to cups. Printing works fine locally using CUPS on the Samba box. What am I missing here? Why can't I print to the Samba box via the Windows and linux clients? Shared directories work fine. I am really frustrated here and have exhausted Google and all other resources I have. Here's my smb.conf for what it's worth.

On Fri, Oct 10, Richard W.M. Jones wrote: > My guess is that the last one (opt/value) will be different for you. Thanks for the pointers. I will poke around. At least augtool on the host seems to behave correctly: olaf@bax:~ $ cd /dev/shm/$$ bash: cd: /dev/shm/3570: Datei oder Verzeichnis nicht gefunden olaf@bax:~ $ mkdir $_ olaf@bax:~ $ cd $_ olaf@bax:/dev/shm/3570 $ mkdir etc

SUSE93 system with these samba packages: kbase3-samba-3.4.0-28 samba-3.0.12-5 samba-client-3.0.12-5 yast2-samba-client-2.11.5-3 yast2-samba-server-2.11.14-3 YAST -> "Security and Users" -> "Firewall" - stop firewall. YAST -> "Network Services" -> "Samba Client" - Workgroup=BAX Desktop -> "Network Browsing" -> "SMB

On Mon, Nov 18, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Mon, Nov 18, 2013 at 10:55 AM, Eric Christopher <echristo at gmail.com> > wrote: >> >> On Sun, Nov 17, 2013 at 6:35 PM, Manman Ren <manman.ren at gmail.com> wrote: >> > Hi Bill, >> > >> > Thanks for the testing case. Most of the time is

On Mon, Nov 18, 2013 at 10:55 AM, Eric Christopher <echristo at gmail.com>wrote: > On Sun, Nov 17, 2013 at 6:35 PM, Manman Ren <manman.ren at gmail.com> wrote: > > Hi Bill, > > > > Thanks for the testing case. Most of the time is spent on debug info > > verifier. > > I fixed a bug in r194974, now it takes too long to run debug info > >

I'm trying to configure a Linux workstation to print to my Samba printserver and can't figure out what I'm missing. Both are running CUPS. Windows clients print fine to the Samba box. Any ideas?

I think that debug info is slowing a self-hosting build down. This build has been going for ages now and shows no sign of quitting. To reproduce, build a Release+Asserts build of clang. Then use that to build a Debug+Asserts version. Include all of the bells and whistles, like the clang-extras and compiler-rt libraries. The reason I suspect debug info is because of this stack trace: [morbo:llvm]

Hi Bill Is this a recent regression? I recently changed the debug info verifier to fix a bug. Thanks, Manman > On Nov 17, 2013, at 5:52 PM, Bill Wendling <isanbard at gmail.com> wrote: > > I think that debug info is slowing a self-hosting build down. This build has been going for ages now and shows no sign of quitting. To reproduce, build a Release+Asserts build of clang. Then

Hi Bill, Thanks for the testing case. Most of the time is spent on debug info verifier. I fixed a bug in r194974, now it takes too long to run debug info verification. Debug info verifier is part of the verifier which is a Function Pass. Tot currently tries to pull all reachable debug info MDNodes in each function, which is too time-consuming. The correct fix seems to be separating debug info

On Sun, Nov 17, 2013 at 6:35 PM, Manman Ren <manman.ren at gmail.com> wrote: > Hi Bill, > > Thanks for the testing case. Most of the time is spent on debug info > verifier. > I fixed a bug in r194974, now it takes too long to run debug info > verification. > > Debug info verifier is part of the verifier which is a Function Pass. Tot > currently tries to pull all

I think it might be. I’m attaching a preprocessed file that can show the problem. Compile it with ToT. $ clang++ -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -m64 -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcovered-switch-default -Wno-uninitialized -Wno-missing-field-initializers -c

Hey Bax, Thank you for the help. I've got a 32 bit system so this is the path I needed. If you have a 64 bit system use the link below this one. https://dl.google.com/linux/talkplugin/rpm/stable/i386/google-talkplugin-5.4.2.0-1.i386.rpm -------- Forwarded Message -------- Subject: Re: [CentOS] google talk plugin for google hangout not loading Date: Thu, 6 Nov 2014 01:02:02 +0100 From:

Hello, i just want to know, when will be Microdowell B BOX N30 ups support? If it planned? Or is any way to get work nut with this device? I am using nut latest stable version. Thank you in your advice! -- Best Regards, Viktorija

Hello, is it to possible to monitor Microdowell B-Box N30 with latest nut? I have tried but wihout any success. Others ups works fine with nut. What about driver to this ups model? Best Regards, Viktorija

Building 1.9.53 fails for me with ocaml 3.10.2 and 3.12.1, likely due to commit a0722c7ad846960be54978a31ebe73b76e119203: [ 318s] ocamlfind ocamlopt -g -warn-error CDEFLMPSUVYZX -package str -I ../src/.libs -I ../ocaml \ [ 318s] mlguestfs.cmxa -linkpkg ../fish/guestfish-progress.o progress-c.o resize_gettext.cmx resize_utils.cmx progress.cmx resize.cmx -cclib -lncurses -o virt-resize