Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #185133 > unrolled thread

systemctl status smb getting stuck

Started byharsh savla <harsh.savla@gmail.com>
First post2017-08-14 01:10 +0200
Last post2017-08-14 01:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.user


Contents

  systemctl status smb getting stuck harsh savla <harsh.savla@gmail.com> - 2017-08-14 01:10 +0200

#185133 — systemctl status smb getting stuck

Fromharsh savla <harsh.savla@gmail.com>
Date2017-08-14 01:10 +0200
Subjectsystemctl status smb getting stuck
Message-ID<ueab7-4ST-9@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

I have a python service which issues the foll. command via a subprocess
call:

RUNLEVEL=1 apt-get install <package>

This package, as part of it's installation, issues a systemctl status smb
command which is getting stuck forever. The reason for giving RUNLEVEL=1 is
to prevent nginx (a dependency of the package) from starting up on port 80
as soon as it is installed since a different service is already bound to
port 80.

OS: Debian 8 Jessie, Python: 2.7.13

Any ideas on what could possibly be wrong? Please ask for more info.

Thanks.

[toc] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web