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

Groups > linux.debian.user > #205025

Re: shell script problem

Show all headers | View raw

On 2/5/2019 4:43 PM, ghe wrote:
> Buster
>
> A shell script has begun to throw errors I can't seem to get rid of.
> Didn't used to -- it started in the past few days.
>
> I have access to a couple Internet connections: a slow but extremely
> reliable T1 I've been with for years, and a Comcast residential cable
> WiFi that's odd, but very fast. There are 2 Ethernet ports on the box.
>
> I wrote a shell script for the frequent and large Buster updates, etc.
> that brings up the Comcast WiFi, makes changes in the DHCP info,
> modifies the routing table so the mirrors in the sources list are routed
> through Comcast, and fires off aptitude.
>
> The problem is that toward the end of bring up Comcast, I get a message
> from systemd saying '-.mount is masked'. The systemd man pages say there
> is indeed something called -.mount and that being masked will kill any
> process encountering a masked something. The message says it's going to
> quit the script.
>

What message?

> Then it goes on with the script, and as best I can tell, finishes properly.
>
> The man pages say there is a way to unmask things (I can't remember what

$systemctl unmask <SERVICE-NAME>

> it is). When I run the command, I'm told that the parameter is wrong (it

Which cmd?

> doesn't like the '-', understandable). I put it in quotes, same thing. I
> try it with something else masked in the list, and it comes back with
> the expected *nix response when all is well (nothing). But when I look
> at the list again, it's still masked.
>
> What's going on? What does 'masked' mean? What is '-.mount'? Should I
> just ignore the error message? Can I ignore any systemd error message?
>

- What's going on -- can't say without seeing the script in question and
the error message you're getting.


In general, ignoring error messages is a recipe for disaster.

--
John Doe

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

shell script problem ghe <ghe@slsware.net> - 2019-02-05 16:50 +0100
  Re: shell script problem john doe <johndoe65534@mail.com> - 2019-02-05 17:20 +0100
    Re: shell script problem ghe <ghe@slsware.net> - 2019-02-05 20:00 +0100
      Re: shell script problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-05 20:10 +0100
        Re: shell script problem ghe <ghe@slsware.net> - 2019-02-05 22:10 +0100
          Re: shell script problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-05 22:10 +0100
            Re: shell script problem ghe <ghe@slsware.net> - 2019-02-05 22:30 +0100
  Re: shell script problem ghe <ghe@slsware.net> - 2019-02-05 19:20 +0100
    Re: shell script problem john doe <johndoe65534@mail.com> - 2019-02-05 19:30 +0100
    Re: shell script problem Jude DaShiell <jdashiel@panix.com> - 2019-02-05 20:30 +0100
    Re: shell script problem John Crawley <john@bunsenlabs.org> - 2019-02-06 06:30 +0100
      Re: shell script problem <tomas@tuxteam.de> - 2019-02-06 11:20 +0100
      Re: shell script problem Rusi Mody <rustompmody@gmail.com> - 2019-02-06 11:20 +0100
      Re: shell script problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-06 15:00 +0100

csiph-web