Re: Security question about daemon-init

:11): avc:  denied  { getattr } for  pid=3104 comm="daemon-init" path="/home/bcv/.thunderbird" dev="dm-5" ino=257 scontext=system_u:system_r:virtd_t:s0 tcontext=system_u:object_r:thunderbird_home_t:s0 tclass=lnk_file permissive=0 I am not sure why on earth

Security question about daemon-init

comm="daemon-init" path="/home/bcv/.thunderbird" dev="dm-5" ino=257 scontext=system_u:system_r:virtd_t:s0 tcontext=system_u:object_r:thunderbird_home_t:s0 tclass=lnk_file permissive=0 I am not sure why on earth would daemon-init try to read .thunderbird directory

Re: Random: CRNG init -->duurt lang

Hoi Paul, On 11/02/2021 19:18, Paul van der Vlis wrote: Hallo, Het booten van een machine gaat nogal traag, dit lijkt te komen doordat er randomness wordt aangemaakt tijdens het booten, want ik zie na ruim een minuut wachten "Random: CRNG init done". De machine heeft blij

Re: Random: CRNG init -->duurt lang

Op 11-02-2021 om 22:15 schreef Richard Lucassen: On Thu, 11 Feb 2021 19:18:41 +0100 Paul van der Vlis wrote: Weet iemand een manier om het booten te versnellen? "haveged" heb ik geïnstalleerd en draai ik als daemon. Dat wil echter nog niet zo helpen, hoe kan ik testen of het randomness heeft

Re: Random: CRNG init -->duurt lang

andom: CRNG init done". En hebben we het over een fysiek computer of over een VM? Fysieke computer. En elke boot of bij boot na installatie? Elke boot. De machine heeft blijkbaar geen hardware-random, want na het booten zie ik: "No TPM or TPM has problems." Het gaat om een HP P

Re: Random: CRNG init -->duurt lang

andom: CRNG init done". De machine heeft blijkbaar geen hardware-random, want na het booten zie ik: "No TPM or TPM has problems." Het gaat om een HP Proliant ML110 G6 met een Xeon processor. Ik vind niets over TPM in het bios. En als ik rng-tools installeer dan klaagt

Re: Random: CRNG init -->duurt lang

On Thu, 11 Feb 2021 19:18:41 +0100 Paul van der Vlis wrote: > Weet iemand een manier om het booten te versnellen? > > "haveged" heb ik geïnstalleerd en draai ik als daemon. Dat wil echter > nog niet zo helpen, hoe kan ik testen of het randomness heeft > aangemaakt? Was het niet een

Re: Random: CRNG init -->duurt lang

On Thu, Feb 11, 2021 at 07:18:41PM +0100, Paul van der Vlis wrote: > Hallo, > > Het booten van een machine gaat nogal traag, dit lijkt te komen doordat er > randomness wordt aangemaakt tijdens het booten, want ik zie na ruim een > minuut wachten "Random: CRNG init done"

Random: CRNG init -->duurt lang

Hallo, Het booten van een machine gaat nogal traag, dit lijkt te komen doordat er randomness wordt aangemaakt tijdens het booten, want ik zie na ruim een minuut wachten "Random: CRNG init done". De machine heeft blijkbaar geen hardware-random, want na het booten zie ik: "No

Re: Cloud-init in Debian

You might have better luck asking on debian-cloud: https://lists.debian.org/debian-cloud/ On December 19, 2020 4:31:22 PM CST, James Allsopp wrote: >Hi, >Does anyone have an example or tutorial for using cloud-init with >debian >images. I'm currently trying to do terraf

Cloud-init in Debian

Hi, Does anyone have an example or tutorial for using cloud-init with debian images. I'm currently trying to do terraform with kvm, but struggling as although terraform picks up the cloud-init, the fqdn and the ssh key isn't working. I'm trying to use this image https://cdimage.debian.org/cdimage

Re: Installing chromium uninstalls runit-init

Quoting Mark Raynsford (2020-02-22 17:38:20) > 'Ello. > > On 2020-02-22T17:32:59 +0100 > Jonas Smedegaard wrote: > > > > Maybe you have... held broken packages? > > > > If you use aptitude instead of apt, then you can step through more > > options, including options involving downgrading

Re: Installing chromium uninstalls runit-init

On Sat, Feb 22, 2020 at 04:51:01PM +, Mark Raynsford wrote: > On 2020-02-22T17:39:15 +0100 > to...@tuxteam.de wrote: > > > > Not all is lost [...] > Thanks! I was about to try that, but it seems that aptitude found an > alternative solution. Firstly, "# aptitude install chromium" said: Great

Re: Installing chromium uninstalls runit-init

t might work. > > Cheers > -- t Thanks! I was about to try that, but it seems that aptitude found an alternative solution. Firstly, "# aptitude install chromium" said: The following packages have unmet dependencies: runit-init : Conflicts: systemd-sysv but 241-7~deb1

Re: Installing chromium uninstalls runit-init

On Sat, Feb 22, 2020 at 04:24:01PM +, Mark Raynsford wrote: > On 2020-02-22T17:08:48 +0100 > wrote: > > I had a similar situation with firefox wanting to install systemd. > > > > Just for kicks, try > > > > apt install chromium sysvinit-core > > > > If that works, you'd perhaps want to

Re: Installing chromium uninstalls runit-init

'Ello. On 2020-02-22T17:32:59 +0100 Jonas Smedegaard wrote: > > Maybe you have... held broken packages? > > If you use aptitude instead of apt, then you can step through more > options, including options involving downgrading (which is unsupported > by Debian, but since your system is already

Re: Installing chromium uninstalls runit-init

Hi Mark, Quoting Mark Raynsford (2020-02-22 17:24:01) > On 2020-02-22T17:08:48 +0100 > wrote: > > I had a similar situation with firefox wanting to install systemd. > > > > Just for kicks, try > > > > apt install chromium sysvinit-core > > > > If that works, you'd perhaps want to adapt your

Re: Installing chromium uninstalls runit-init

On 2020-02-22T17:08:48 +0100 wrote: > I had a similar situation with firefox wanting to install systemd. > > Just for kicks, try > > apt install chromium sysvinit-core > > If that works, you'd perhaps want to adapt your apt-preferences > (either pushing sysvinit-core or lowering systemd). >

Re: Installing chromium uninstalls runit-init

On Sat, Feb 22, 2020 at 04:02:16PM +, Mark Raynsford wrote: > Hello! > > Attempting to install chromium results in the following: > > # apt install chromium I had a similar situation with firefox wanting to install systemd. Just for kicks, try apt install chromium sysvinit-core If that

Installing chromium uninstalls runit-init

-string-perl xml-twig-tools nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver nvidia-legacy-304xx-vdpau-driver The following packages will be REMOVED: runit-init The following NEW packages will be installed: adwaita-icon-theme at-spi2-core chromium chromium-common chromium-sandbox dbus-user

Re: [Better Solution] how to switch a Debian buster system from systemd to sys-v init

> On Jun 27, 2019, at 12:42 AM, Rick Thomas wrote: > > > >> On Jun 25, 2019, at 11:20 PM, Jonas Smedegaard wrote: >> >> Seems this would work as well, with less collateral damage: >> >> apt install -y sysvinit-core elogind >> apt --purge autoremove >> > > This works great and, as

Re: [Better Solution] how to switch a Debian buster system from systemd to sys-v init

> On Jun 25, 2019, at 11:20 PM, Jonas Smedegaard wrote: > > Seems this would work as well, with less collateral damage: > > apt install -y sysvinit-core elogind > apt --purge autoremove > This works great and, as noted, is far more elegant. Thanks, Jonas! Rick

Re: [Solved - sorta - part 2] Re: how to switch a Debian buster system from systemd to sys-v init

Quoting Rick Thomas (2019-06-26 09:13:37) > Hi Jonas, > > > On Jun 25, 2019, at 11:20 PM, Jonas Smedegaard wrote: > > > > Would be helpful to know if those experiencing long pause in > > dbus-depending environments had _no_ dbus installed (and actively > > running) or had it running with

Re: [Solved - sorta - part 2] Re: how to switch a Debian buster system from systemd to sys-v init

Hi Jonas, > On Jun 25, 2019, at 11:20 PM, Jonas Smedegaard wrote: > > Would be helpful to know if those experiencing long pause in > dbus-depending environments had _no_ dbus installed (and actively > running) or had it running with elogind. How can I tell which situation I have? Thanks!

Re: [Solved - sorta - part 2] Re: how to switch a Debian buster system from systemd to sys-v init

g a Debian buster system from systemd to sysv init. > > > > The short version [1]: > > > > apt-get install -y sysvinit-core > > So our goal is to start with a working Debian buster system with the > Mate desktop using the systemd init, and convert

Re: [Solved - sorta - part 2] Re: how to switch a Debian buster system from systemd to sys-v init

Rick Thomas wrote: > > In any case, the solution I came up with is > > apt-get --purge install -y sysvinit-core dbus- glib-networking- > libgtk-3-0- > apt-get --purge autoremove > > Note the trailing minus-signs on dbus- glib-networking- libgtk-3-0- These > packages need to be

[Solved - sorta - part 2] Re: how to switch a Debian buster system from systemd to sys-v init

> On Jun 23, 2019, at 2:24 AM, to...@tuxteam.de wrote: > > On Sat, Jun 22, 2019 at 05:45:39PM -0700, Rick Thomas wrote: >> >> Purely out of curiosity, I'd like to see what's involved in >> switching a Debian buster system from systemd to sysv init. > > The

[Solved - sorta - part 1] Re: how to switch a Debian buster system from systemd to sys-v init

> On Jun 23, 2019, at 2:24 AM, to...@tuxteam.de wrote: > > On Sat, Jun 22, 2019 at 05:45:39PM -0700, Rick Thomas wrote: >> >> Purely out of curiosity, I'd like to see what's involved in >> switching a Debian buster system from systemd to sysv init. > > The

Re: How to change init from sysv to systemd

On Sun, 23 Jun 2019, Bob Bernstein wrote: How should I approach this change with an eye to maximum safety? Again, the wiki proved spot on: https://wiki.debian.org/systemd#Installing_and_Testing Sorry about the false alarm. Thank you -- These are not the droids you are looking for.

Re: How to change init from sysv to systemd

On Sun, 23 Jun 2019 14:55:58 -0400 Bob Bernstein wrote: > I encountered an error during the install of a deb which > led me to the discovery that my current init system is > still sysvinit. > > The error was: > > /sbin/init: invalid option -- '-' > Usage: init {-e

How to change init from sysv to systemd

I encountered an error during the install of a deb which led me to the discovery that my current init system is still sysvinit. The error was: /sbin/init: invalid option -- '-' Usage: init {-e VAR[=VAL] | [-t SECONDS] {0|1|2|3|4|5|6|S|s|Q|q|A|a|B|b|C|c|U|u}} Thanks to the wiki: https

Re: how to switch a Debian buster system from systemd to sys-v init

On Sun, Jun 23, 2019 at 01:27:08PM +0200, arne wrote: > > > That's right. "Modern" desktop environments (Gnome and derivatives, > > most probably also KDE) depend these days on systemd. I don't know > > how hard those dependencies are -- you'd want to look at Devuan [2] > > [3] to see how far

Re: how to switch a Debian buster system from systemd to sys-v init

> That's right. "Modern" desktop environments (Gnome and derivatives, > most probably also KDE) depend these days on systemd. I don't know > how hard those dependencies are -- you'd want to look at Devuan [2] > [3] to see how far they went, if at all, into fixing this. The Devuan default

Re: how to switch a Debian buster system from systemd to sys-v init

On Sat, Jun 22, 2019 at 05:45:39PM -0700, Rick Thomas wrote: > > Purely out of curiosity, I'd like to see what's involved in > switching a Debian buster system from systemd to sysv init. The short version [1]: apt-get install -y sysvinit-core > Please, I don't want to restart or

how to switch a Debian buster system from systemd to sys-v init

Purely out of curiosity, I'd like to see what's involved in switching a Debian buster system from systemd to sysv init. Please, I don't want to restart or get involved in any of the existing systemd/sysv flame wars. I'm *just curious* to see if it would work? First of all, is this even

Re: Broken Debian's testing migration (grave bug in module-init-tools)

migration to testing. > > A grave bug in the testing version of module-init-tools (3.12~pre2-1) > was fixed several weeks ago, and the package was uploaded with > urgency=high: > > module-init-tools (3.12~pre2-2) unstable; urgency=high > >* Fixed an init scripts dependency

Re: /lib/lsb/init-functions on LXC servers

Hi Reco, On 02/14/18 14:55, Reco wrote: True. There's one tiny bit though - try pidof -o %PPID -x /usr/sbin/sshd and watch it output several pids as well. Yes, indeed. If pidofproc would rely upon the pidfile only, then there is no reason to call pidof. And you don't have to spawn yet

Re: /lib/lsb/init-functions on LXC servers

Hi. On Wed, Feb 14, 2018 at 02:33:16PM +0100, Harald Dunkel wrote: > Hi Reco, > > wrt "pgrep --ns 1 -f /usr/sbin/sshd": > > The executable path simply doesn't tell if this is the right service > to stop. If I run 2 services in parallel (e.g. for different network > interfaces), then

Re: /lib/lsb/init-functions on LXC servers

Hi Reco, wrt "pgrep --ns 1 -f /usr/sbin/sshd": The executable path simply doesn't tell if this is the right service to stop. If I run 2 services in parallel (e.g. for different network interfaces), then this approach is already broken. Sample: # pgrep --ns 1 -f /usr/sbin/sshd 12602 # ps -ef |

Re: /lib/lsb/init-functions on LXC servers

Hi. On Mon, Feb 05, 2018 at 04:04:37PM +0100, Harald Dunkel wrote: > Hi Reco, > > you mean this is a known issue??? Well, it's known to me (since then) at least as I merely read the contents of /lib/lsb/init-functions in my Debian system. Pinpointing the problem is easy, anyon

Re: /lib/lsb/init-functions on LXC servers

Hi Reco, you mean this is a known issue??? Harri

Re: /lib/lsb/init-functions on LXC servers

Hi. On Fri, Feb 02, 2018 at 11:35:04AM +0100, Harald Dunkel wrote: > Hi folks, > > I see a weird effect of pidofproc (defined in /lib/lsb/init-functions): > If there is no local daemon with a given search path running, then it > returns the PIDs the daemons running in the

/lib/lsb/init-functions on LXC servers

Hi folks, I see a weird effect of pidofproc (defined in /lib/lsb/init-functions): If there is no local daemon with a given search path running, then it returns the PIDs the daemons running in the LXC containers. AFAICT this affects the startup scripts of apache2 opensmtpd

Re: conflit entre init et unbound

❦ 2 octobre 2017 10:43 +0200, bernard.schoenac...@free.fr : > et c'est dnscrypt-proxy qui prend le dessus ... Du coup, soit le désinstaller, soit désactiver sa socket (systemctl disable dnscrypt-proxy.socket). -- The mind is its own place, and in itself Can make a Heav'n of Hell, a Hell of

Re: conflit entre init et unbound

- Mail original - > De: "Vincent Bernat" <ber...@debian.org> > À: debian-user-french@lists.debian.org > Envoyé: Lundi 2 Octobre 2017 08:41:06 > Objet: Re: conflit entre init et unbound > > ❦ 1 octobre 2017 11:24 +0200, bernard.schoenac...@free.

Re: conflit entre init et unbound

❦ 1 octobre 2017 11:24 +0200, bernard.schoenac...@free.fr : >> > tcp0 0 127.0.2.1:530.0.0.0:* >> > LISTEN 1/init >> > >> > merci pour vos lumières >> > > apt-cache policy dnss > dnss: > Instal

Re: conflit entre init et unbound

- Mail original - > De: "bernard schoenacker" <bernard.schoenac...@free.fr> > À: debian-user-french@lists.debian.org > Envoyé: Dimanche 1 Octobre 2017 11:24:15 > Objet: Re: conflit entre init et unbound > > > > - Mail original - >

Re: conflit entre init et unbound

- Mail original - > De: "Vincent Bernat" <ber...@debian.org> > À: debian-user-french@lists.debian.org > Envoyé: Dimanche 1 Octobre 2017 11:06:34 > Objet: Re: conflit entre init et unbound > > ❦ 30 septembre 2017 18:06 +0200, bernard.schoenac...@f

Re: conflit entre init et unbound

0 0 127.0.2.1:530.0.0.0:* LISTEN > 1/init > > merci pour vos lumières Si dnss est installé, le retirer. -- Wrinkles should merely indicate where smiles have been. -- Mark Twain signature.asc Description: PGP signature

Re: conflit entre init et unbound

r la situation afin que unbound puisse prendre >>>> la main sur le port 53 ? >>>> >>>> netstat -antp | grep :53 >>>> | >>>> tcp0 0 127.0.2.1:530.0.0.

Re: conflit entre init et unbound

r le port 53 ? >>> >>> netstat -antp | grep :53 >>> | >>> tcp0 0 127.0.2.1:530.0.0.0:* LISTEN >>> 1/init >>> >>> merci pour vos lumière

Re: conflit entre init et unbound

>>| >> tcp0 0 127.0.2.1:53 0.0.0.0:* LISTEN >>1/init >> >> merci pour vos lumières >> >> slt >> bernard >> > > Euh pour quelle mauvaise raison init écouterait sur 53/tcp > Voire même écoute sur le réseau ? > C'est quoi init ? Ph. Gras

Re: conflit entre init et unbound

> tcp0 0 127.0.2.1:530.0.0.0:* LISTEN > 1/init > > merci pour vos lumières > > slt > bernard > Euh pour quelle mauvaise raison init écouterait sur 53/tcp Voire même écoute sur le réseau ?

conflit entre init et unbound

bonjour, comment faire pour débloquer la situation afin que unbound puisse prendre la main sur le port 53 ? netstat -antp | grep :53 | tcp0 0 127.0.2.1:530.0.0.0:* LISTEN 1/init merci

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Jonathan de Boyne Pollard <j.deboynepollard-newsgro...@ntlworld.com> wrote: > Sven Hartge: >> systemd happily runs "legacy" LSB init scripts >> > ... except when its one-size-fits-all approach does not work, of > course. Example: > * https:/

Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Sven Hartge: systemd happily runs "legacy" LSB init scripts ... except when its one-size-fits-all approach does not work, of course. Example: * https://unix.stackexchange.com/questions/386846/ This is the problem with even Mewburn rc scripts (as I can attest from personal

Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Tom Browder: # systemctl enable postfix # systemctl daemon-reload Minor note: enable incorporates a daemon-reload.

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Christian Seiler <christ...@iwakd.de> wrote: > Now, that doesn't mean that you should still write _new_ init scripts > for custom services if you're going to use systemd anyway. There it > will be a good idea to learn how to do that with native systemd > service units. Ex

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Am 2017-08-21 11:52, schrieb Tom Browder: On Mon, Aug 21, 2017 at 02:36 Sven Hartge <s...@svenhartge.de> wrote: Question: Why do you want to manually replace the init-script from postfix in Jessie with a systemd.unit? What do you want to accomplish by doing so (other than creating a po

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

> So the question I have is how does it all work? There is no init.d, >>> but there seems to be some convoluted handling that I haven't >>> figured out yet. Surely some expert can write a postfix.service >>> file that drives postfix commands. >> Question: Why do you wa

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

it.d, > > but there seems to be some convoluted handling that I haven't figured > > out yet. Surely some expert can write a postfix.service file that > > drives postfix commands. ... > Question: Why do you want to manually replace the init-script from > postfix in Jessie wi

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

emplate. This is coupled with a generator, "postfix-instance-generator" which creates new instances on the fly, based on the output of "postmulti -l -a". I don't know if you could transplant this mechanism from postfix3 (version in Stretch) to postfix2 (version in Jessie). Questi

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote: > Tom Browder wrote: > > > The contents of the postfix.service file are; > ... > That unit file does effectivly nothing. It just starts "/bin/true" and > exits. > > What it *not* does is starting

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote: > Tom Browder wrote: > > > The contents of the postfix.service file are; > ... > > That unit file does effectivly nothing. It just starts "/bin/true" and > exits. > > What it *not* does is starting

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Tom Browder wrote: > The contents of the postfix.service file are; > [Unit] > Description=Postfix Mail Transport Agent > Conflicts=sendmail.service exim4.service > ConditionPathExists=/etc/postfix/main.cf > [Service] > Type=oneshot > RemainAfterExit=yes >

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

On Sun, Aug 20, 2017 at 11:41 AM, Nicolas George wrote: > Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit : >> So "disabled" is normal? > > Indeed. See: > >

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit : > So "disabled" is normal? Indeed. See: https://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/ch-Services_and_Daemons.html#s3-services-configuration-enabling Regards, -- Nicolas George signature.asc Description: Digital

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

On Sun, Aug 20, 2017 at 10:17 AM, Nicolas George wrote: > Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit : >> > # systemctl start postfix >> > # systemctl status postfix >> > >> > and got several lines basically saying posfix.service was disabled. > >> The exact message

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

On Sun, Aug 20, 2017 at 10:17 Nicolas George wrote: > Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit : > > > # systemctl start postfix > > > # systemctl status postfix > > > > > > and got several lines basically saying posfix.service was disabled. > > > The exact

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit : > > # systemctl start postfix > > # systemctl status postfix > > > > and got several lines basically saying posfix.service was disabled. > The exact message is: > > * postfix.service - Postfix Mail Transport Agent >Loaded: loaded

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit : > I got a postfix.service file from a postfix developer and installed it in > /etc/systemd/system as the docs mention. > > I then moved the /etc/init.d/postfix file away, reloaded the systemd > daemon, and did: > > # systemctl start postfix

Re: Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

On Sun, Aug 20, 2017 at 9:42 AM, Tom Browder wrote: > I got a postfix.service file from a postfix developer and installed it in > /etc/systemd/system as the docs mention. > > I then moved the /etc/init.d/postfix file away, reloaded the systemd daemon, > and did: > > #

Systemd: Error when replacing postfix LSB init with postfix.service on Debian 8 (jessie)

I got a postfix.service file from a postfix developer and installed it in /etc/systemd/system as the docs mention. I then moved the /etc/init.d/postfix file away, reloaded the systemd daemon, and did: # systemctl start postfix # systemctl status postfix and got several lines basically

Re: Systemd and Init was Problems communicating with and between servers after upgrade - correction

and does *not* have systemd unit files, it falls back to the sysvinit scripts. Thanks Greg That makes sense. Does this mean init will disappear from Debian in a future release? It is interesting that you gave ssh as an example because we seem to have encountered strange problems with mixed IDE

Re: Systemd and Init was Problems communicating with and between servers after upgrade - correction

On Mon, Sep 12, 2016 at 07:32:52PM +0100, Clive Menzies wrote: > However, studying documentation on systemd v init, I'm a bit confused. I > assumed the reinstall would implement systemd for all services and init > wouldn't be visible although symlinks will use init where necessary.

Systemd and Init was Problems communicating with and between servers after upgrade - correction

s server_U is working after reinstallation, following much exploration, we reinstalled jessie 8.3 on server_M and committed to systemd to avoid potential progressive sysv-init problems we'd learned of during our investigation. After a reinstall of the system and subsequently samba (twice), w

Re: Curiosidade: init-d-script(5)

; codificado no framework: /lib/init/init-d-script. A propósito, ele possui > até mesmo uma man page: man init-d-script. > > O que causou estranheza foi o fato de observar que nenhum outro script que > verifiquei (ex: bind9, apache, proftpd, exim4, cron, ...) utiliza-o. Fato > que

Curiosidade: init-d-script(5)

Devido a necessidade de criar um script para inicializar um determinado serviço, comecei por /etc/skeleton e descobri, através dele, que não precisava codificar praticamente nada, pois tudo já estava cuidadosamente codificado no framework: /lib/init/init-d-script. A propósito, ele possui até

Re: pregunta sobre iptables, init i systemd

tema també m'ha servit per començar a aprendre els bàsics de systemd. Salut Àlex A 2016-06-05 21:30, Àlex escrigué: Benvolguts/des debianites, em podeu aconsellar sobre quin és el millor mètode per fer regles d'iptables persistents ara que systemd substitueix init a Debian Testing

Re: pregunta sobre ip. ,,tables, init i systemd

Disculpeu la brevetat, enviat des del telèfon mobil Oscar Osta Pueyo wrote: >Bones, > >El dia 6 juny 2016 15:12, "Alex Muntada" va escriure: >> >> Àlex: >> >> > Encara he trobat una tercera manera, >> > >> >   https://wiki.debian.org/iptables >> >>

Re: pregunta sobre iptables, init i systemd

Disculpeu la brevetat, enviat des del telèfon mobil Oscar Osta Pueyo wrote: >Bones, > >El dia 6 juny 2016 15:12, "Alex Muntada" va escriure: >> >> Àlex: >> >> > Encara he trobat una tercera manera, >> > >> >   https://wiki.debian.org/iptables >> >>

Re: pregunta sobre iptables, init i systemd

Bones, El dia 6 juny 2016 15:12, "Alex Muntada" va escriure: > > Àlex: > > > Encara he trobat una tercera manera, > > > > https://wiki.debian.org/iptables > > Jo utilitzo aquesta manera (if-pre-up.d) des de fa temps i no > dóna gaires maldecaps (potser algun cop amb alguna

Re: pregunta sobre iptables, init i systemd

Àlex: > Encara he trobat una tercera manera, > > https://wiki.debian.org/iptables Jo utilitzo aquesta manera (if-pre-up.d) des de fa temps i no dóna gaires maldecaps (potser algun cop amb alguna interfície hotplug de la que no conec el nom i que no tinc a les iptables). > Seria aquesta la

Re: pregunta sobre iptables, init i systemd

On Sun, Jun 05, 2016 at 10:46:03PM +0200, Josep Ma. Ferrer wrote: > El Diumenge 05 Juny 2016, a les 21:30:43, Àlex va escriure: > > Benvolguts/des debianites, > > > > em podeu aconsellar sobre quin és el millor mètode per fer regles > > d'iptables persistents ara q

Re: pregunta sobre iptables, init i systemd

El Diumenge 05 Juny 2016, a les 21:30:43, Àlex va escriure: > Benvolguts/des debianites, > > em podeu aconsellar sobre quin és el millor mètode per fer regles > d'iptables persistents ara que systemd substitueix init a Debian Testing? > > Sempre que he establert regles de talla

Re: pregunta sobre iptables, init i systemd

On 05/06/16 21:30, Àlex wrote: > > Benvolguts/des debianites, > > > > em podeu aconsellar sobre quin és el millor mètode per fer regles > > d'iptables persistents ara que systemd substitueix init a Debian Testing? > > > > Sempre que he establert regles de tallafocs, les escrivi

Re: pregunta sobre iptables, init i systemd

que systemd substitueix init a Debian Testing? > > Sempre que he establert regles de tallafocs, les escrivia a un script > dintre de /etc/init.d/regles_tallafocs.sh i feia un update-rc.d > regles_tallafocs.sh defaults i tot funcionava. > > Però els temps canvien i avui no m'ha f

pregunta sobre iptables, init i systemd

Benvolguts/des debianites, em podeu aconsellar sobre quin és el millor mètode per fer regles d'iptables persistents ara que systemd substitueix init a Debian Testing? Sempre que he establert regles de tallafocs, les escrivia a un script dintre de /etc/init.d/regles_tallafocs.sh i feia un update

Re: Ayuda con gnokii Telephone interface init failed: Command timed out.

. > > ¿Pero cuál demonio?, gnokii no lo arranco como demonio. Pues a mano, como sea que lo inicies :-) >> http://wiki.gnokii.org/index.php/Debug_output > > En este caso añadi las lineas siguientes al final de mi archivo de > configuracion .gnokiirc > > [logging] > debug

Re: Ayuda con gnokii Telephone interface init failed: Command timed out.

al arrancar el sistema, gnokii me lanza un error. >>> >>> Telephone interface init failed: Command timed out. >>> >>> Ya verifique el archivo de configuracion y se encuentra en perfecto >>> estado, pero por la IMPORTANCIA de su funcion, recurro a ustedes para &

Re: Ayuda con gnokii Telephone interface init failed: Command timed out.

2016-03-29 7:50 GMT-06:00 Camaleón <noela...@gmail.com>: > El Mon, 28 Mar 2016 20:49:00 -0600, Debia Linux escribió: > > (...) > >> El problema es que al arrancar el sistema, gnokii me lanza un error. >> >> Telephone interface init failed: Command timed o

Re: Ayuda con gnokii Telephone interface init failed: Command timed out.

El día 29 de marzo de 2016, 8:50, Camaleón <noela...@gmail.com> escribió: > El Mon, 28 Mar 2016 20:49:00 -0600, Debia Linux escribió: > > (...) > >> El problema es que al arrancar el sistema, gnokii me lanza un error. >> >> Telephone interface init failed: Comm

Re: Ayuda con gnokii Telephone interface init failed: Command timed out.

El Mon, 28 Mar 2016 20:49:00 -0600, Debia Linux escribió: (...) > El problema es que al arrancar el sistema, gnokii me lanza un error. > > Telephone interface init failed: Command timed out. > > Ya verifique el archivo de configuracion y se encuentra en perfecto > e

Ayuda con gnokii Telephone interface init failed: Command timed out.

funcionando. El problema es que al arrancar el sistema, gnokii me lanza un error. Telephone interface init failed: Command timed out. Ya verifique el archivo de configuracion y se encuentra en perfecto estado, pero por la IMPORTANCIA de su funcion, recurro a ustedes para encontrar una solucion mas

Re: dselect, init and systemd-sysv

On Sun, 17 Jan 2016 11:26:54 +0100 Aldo Maggi <aldoma...@katamail.com> wrote: > Yesterday while updating my system via dselect (I'm using testing) > I've received the warning that "init and systemd-sysv" were going to > be uninstalled and I had to approve or de

Re: dselect, init and systemd-sysv

On Sun, 17 Jan 2016 12:00:02 +0100, Aldo Maggi wrote: > Yesterday while updating my system via dselect (I'm using testing) I've > received the warning that "init and systemd-sysv" were going to be > uninstalled and I had to approve or deny that action. > I've thought tha

dselect, init and systemd-sysv

Yesterday while updating my system via dselect (I'm using testing) I've received the warning that "init and systemd-sysv" were going to be uninstalled and I had to approve or deny that action. I've thought that as in previous cases (to be frank not recently but many

dselect, init and systemd-sysv

Yesterday while updating my system via dselect (I'm using testing) I've received the warning that "init and systemd-sysv" were going to be uninstalled and I had to approve or deny that action. I've thought that as in previous cases (to be frank not recently but many

Re: How to install init scripts manually?

, 04 aug 14, 13:30:54, Martin T wrote: >> >> As a next step, I made the /etc/init.d/test-script file executable and >> added a symlink to /etc/rc3.d/("ln -s ../init.d/test-script >> /etc/rc3.d/S23test-script") directory and changed my runlevel from >> 2(def

Re: something at init is taking about 31s to finish

On 2015-08-31, wrote: > >> I understand the whole "oh noes, firmware is a binary blob with unknown >> contents [...] > > It seems you don't :-) > >> By not installing the firmware package, you are just making your life >> harder without gaining anything but a

  1   2   3   4   5   6   7   8   9   10   >