similar to: SysV interface script

During converting a client from one machine to another, I need to run Samba on both versions. The snag is, for various reasons I need to keep the same hostname on both machines (they refer to each other by different names. and do not use DNS). If it helps, it's Solaris 2.5.1 & 2.6, and the Samba is 1.9.17p4. How can I make them both visible, uniquely, whilst retaining the same host name

OK, med 19:00 sv tid /Lennart At 13:05 1998-11-07 +1100, you wrote: > SAMBA Digest 1867 > >For information on unsubscribing see http://samba.anu.edu.au/listproc >Topics covered in this issue include: > > 1) Re: nis homedir troubles > by Jeremy Allison <jallison@cthulhu.engr.sgi.com> > 2) calling all Samba vendors! > by Andrew Tridgell

DM Review and Geac Present: One Size Does Not Fit All - Implementing the Right Performance Management Solution Date: April 22, 2004 Time: 12:00 p.m. - 1:00 p.m. ET 9:00 a.m. - 10:00 a.m. PT Companies of all sizes and revenue bands are discovering that their traditional point solutions for budgeting, planning, and reporting have become inadequate for answering the challenges posed by

Author: jpk Repository: /hg/zfs-crypto/gate Revision: e7e07b2f4fcfbe725493f4074f9e9f0d8bfd8e1c Log message: PSARC/2002/762 Layered Trusted Solaris PSARC/2005/060 TSNET: Trusted Networking with Security Labels PSARC/2005/259 Layered Trusted Solaris Label Interfaces PSARC/2005/573 Solaris Trusted Extensions for Printing PSARC/2005/691 Trusted Extensions for Device Allocation PSARC/2005/723 Solaris

Hi All, When our server receives simultaneous print jobs from 2 or more clients, the print service stalls and I have to manually restart it (lpsched). I am running Samba 2.0.4b under Solaris 2.5.1 on a SPARC 20 and I'm using system V printing. The printers are connected to the ethernet using HP Jetdirect cards and administered by jetadmin on the Sun box. Any ideas on how I could troubleshoot

Hi I'm running Samba 2.2.8a on a UnixWare 7.1.3 box. I'd set up the Samba printer shares, and it seemed to be working fine (only live for a couple of weeks). However, I've just added some heavy users, and the printer daemon keeps bombing out. I'd configured the printers to use lpr, but someone suggested I should use lp, so I thought I'd give this a go at the weekend.

Hi folks, I have a print server, running SPARC Solaris 9. I've just upgraded from Samba 3.0.10 to 3.0.22 and immediately hit system load issues which appear to be related to the use of "lpstat -v" to determine the available print queues. There are about 70 Unix print queues on this system. Running "lpstat -v" can take something like 20s of wall-clock time. lpstat

I have a problem going on here, that I hope someone out there may be able to help solve. We run SAMBA 1.16p11 under Solaris 2.5 to serve about 60 Win95 clients. Thirty of these clients are printing to three HP laserjet printers, each printer with a JetDirect card which uses lpsched on the Solaris server as their print spooler. These spools have been defined as BSD-type devices under sysv's

Hello, Is it possible to set up a printer on a Sun Solaris (sparc 2.6) machine and have it properly print to an HP Laserjet printer without the use of jetdirect? I'm trying to print to an NT controlled printer using Samba on the Sun machine. I've been trying to utilize the "smbprint" command, however I'm having all kinds of problems. On the Sun machine, I add the printer

Dear Steve, RE: > sorry to ask this question, which is really about Solaris printer > administration, here but i've looked everywhere else i can think of to no > avail. i've got a LaserJet 1100 hooked up to a Solaris box and i want to > print to it from W98 clients. for this to happen, the PCL coming from the > W98 boxes needs to be passed through the print system

This is my way of filtering ^D and PCL headers out of samba jobs on a solaris 7 system. It assumes that all your printers are capable of postscript, and that you are using PS drivers on any printers are not PCL capable. 1) Add a declaration of pcl capability to the relevant printers: lpadmin -p hp8000 -I 'simple,postscript,pcl' Choose which printers you do this to carefully, Using

After building and install dovecot I then made my own self signed SSL certs and placed them carefully into the correct places : Thus : # grep -v "^#" dovecot-openssl.cnf | grep -v "^$" [ req ] default_bits = 1024 encrypt_key = yes distinguished_name = req_dn x509_extensions = cert_type prompt = no [ req_dn ] C=CA ST=Ontario L=Toronto O=Blastwave OU=IMAP server

Our company manufactures an E1 channel bank that is approved for use in Australia (it should also be compatible with Euro standards). It is modular and available in 10, 20 or 30 analog port configurations. Signal monitoring and configuration is via Ethernet. These units are manufactured in low quantities for specific telco requirements. However if there was enough interest, we would be able to

Hi all, I'm using asterisk in a production environment now and this afternoon I got reports complaining that it was not working. Looking at the asterisk console output, I saw it contains lots of error messages as printed below. Unfortunately it is not obvious from the logs as to what started all this. Just before the error messages start, everything seems to be working fine with no problems.

Dear users Thanks for reading this. Hope you will help me. I am using samba 1.9.17p2 on SunSparc-20 running solaris2.5.1 for printing and file sharing with PC-network. File sharing is working fine but I want to print to a WfWg printer from Solaris. So I have used your script smbprint.sysv and try to print. But I am facing following problems: 1-

Dear Sir/Madam, I've downloaded the samba 2.2.2 for solaris, and use pkgadd install it, but I can't find smbprint or smbprint.sysv script in this package. could you help me? thanks and regards, David -------------- next part -------------- HTML attachment scrubbed and removed

On Thu, Dec 12, Pino Toscano wrote: > What do you think? I think that your Should-Start handling is broken. Required means the given file can not properly work without the listed servers, insserv will error out. Should means it can very well work without them if they are not present or enabled. Otherwise the given file has to be scheduled after the listed services. Olaf

On Thu, Dec 12, Pino Toscano wrote: > On Thursday 12 December 2013 14:49:36 Olaf Hering wrote: > > On Thu, Dec 12, Pino Toscano wrote: > > > What do you think? > > > > I think that your Should-Start handling is broken. Required means the > > given file can not properly work without the listed servers, insserv > > will error out. Should means it can very

On Thursday 12 December 2013 15:01:07 Olaf Hering wrote: > On Thu, Dec 12, Pino Toscano wrote: > > On Thursday 12 December 2013 14:49:36 Olaf Hering wrote: > > > On Thu, Dec 12, Pino Toscano wrote: > > > > What do you think? > > > > > > I think that your Should-Start handling is broken. Required means > > > the > > > given file can

On Thu, Dec 12, Pino Toscano wrote: > Sure, but as a Should-Start means it is a weak dependency, and can be > skipped, which is what I don't want. Are you saying in Debian the Should-Start is not handled properly? Even if Should-Start is weak it still has to be taken into account. Olaf