similar to: SysV style printer interface (Works atleast in SCO)

Hey, I worked for days on this, and I want to share the solution I stubled across. I got this error message from my wife XP laptop: "Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for

Hi, I''m having problems with new Shorewall installation on Fedora Core 3 (had same problem with Core 2 and upgrade did not help even iptables was upgraded from 1.2.9 to 1.2.11). I''ve followed two nic example, but starting Shorewall drops all connections and don''t permit any outgoing requests, even with "all allowed" policy. Policy file is below. Current setup

If you have any quicknet cards you are not using, I may be interested in them. I'll discuss terms after I know what you have. For sake of high shipping costs, I'm not interested in overseas shipments to the United States (where I live). My best resources will be for those that have PCI PhoneJacks, or PCMCIA CardJacks. Please reply to my email address, and not the mailing list.

Hi, we are using samba 3.0.24 as a printspooler for 80 network printers with a 500kB ntprinters.tdb for some years now. When we recently restarted samba we noticed that the ntprinters.tdb automatically shrinked to 24kB and printing was no longer possible. tdbdump of the original tdb-file is impossible too: "Failed to open ntprinters.tdb" The strange thing about this: we can solve

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

On Thursday 12 December 2013 16:27:30 Olaf Hering wrote: > 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. No,

Turn the rc.d symlinks for the guestfs-firstboot service as relative, instead of absolute paths: the result is the same (the service works the same), and this way is more coherent with symlinks created by update-rc.d. --- customize/firstboot.ml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/customize/firstboot.ml b/customize/firstboot.ml index 52dfbbe..706d63c 100644

On 12/29/2015 10:13 AM, Mike - st257 wrote: > Hello CentOS List, > > I have a server that has SysV script supplied by a hardware manufacturer, > which is not functioning properly. From my reading, systemd-sysv-generator > should handle them (like it did for Dell OpenManage software which supplied > SysV init scripts). > >

> The particular software in question is LSI MegaRaid SNMP daemon. > I retrieved the latest version from LSI's site which was provided for EL7. While I don't have the answer to your specific question, LSI does does not advertise support for the latest point release and using their current version faults for me after upgrading a host. You say "not functioning properly" but

On 12/29/2015 09:13 AM, Mike - st257 wrote: > ~]# /etc/init.d/lsi_mrdsnmpd start > Reloading systemd: [ OK ] > Starting lsi_mrdsnmpd (via systemctl): Failed to start > lsi_mrdsnmpd.service: Unit lsi_mrdsnmpd.service failed to load: No such > file or directory. > [FAILED] IIRC,

Instead of converting the sysv script, you could trivially write your own, the following was tested against about 6 SNMP queries, the service stops and starts as expected. You may want to purge the sysv remnants. # cat /etc/systemd/system/lsi_mrdsnmpd.service [Unit] Description=LSI SNMP Agent startup/shutdown script Requires=network.target Requires=snmpd.service After=network.target

On 30 Dec 2015 00:55, "Mike - st257" <silvertip257 at gmail.com> wrote: > > On Tue, Dec 29, 2015 at 5:23 PM, Joseph L. Casale < jcasale at activenetwerx.com > > wrote: > > > Instead of converting the sysv script, you could trivially write your own, > > the following > > was tested against about 6 SNMP queries, the service stops and starts as >

On 30 December 2015 at 14:23, Mike - st257 <silvertip257 at gmail.com> wrote: > Consolidating my reply to both James and Gordon in one message. > > > On Wed, Dec 30, 2015 at 2:38 AM, James Hogarth <james.hogarth at gmail.com> > wrote: > > > On 30 Dec 2015 00:55, "Mike - st257" <silvertip257 at gmail.com> wrote: > > > > > > On

On 30 December 2015 at 15:25, Mike - st257 <silvertip257 at gmail.com> wrote: > On Wed, Dec 30, 2015 at 10:06 AM, James Hogarth <james.hogarth at gmail.com> > wrote: > > > > > > > Best way to see this is using systemctl (status|cat|show) > <servicename> > > > ... > > > > > > > > I expect if you do this for your

On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at dea.spamcon.org> wrote: Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV initscript for whether it is running interactively, instead of at boot time, no longer works. Under CentOS 7 / systemd, is there some way for the initscript to know this? Generally "interactive" init scripts are not in any way