Opened 18 years ago

Closed 18 years ago

#1809 closed defect (fixed)

blfs bootscript error in netfs, 'IGTERM unknown signal'

Reported by: ken@… Owned by: blfs-book@…
Priority: normal Milestone: 6.2.0
Component: Bootscripts Version: SVN
Severity: minor Keywords:
Cc:

Description

When shutting down, the netfs bootscript provokes this error message, but since we don't really expect SIGTERM to do a lot, the script carries on successfully. Looking at this, there seem to be several issues here:

(i) in the grep to find NETMOUNTS, '|\' for '\|'

(ii) the cause of the error message, fuser -m -SIGTERM $NETMOUNTS : this doesn't report an error if I change it to --SIGTERM so probably the psutils manpage is wrong, or perhaps it's an error in the fuser code.

(iii) the sed to format NETMOUNTS is probably not doing what is intended - I have nfs mounts on /sources and /mnt/av, NETMOUNTS contains /sources /mnt/av

I've fixed the first two, patch at http://www.linuxfromscratch.org/~ken/misc/bootscripts-netfs-fix-patch but the third item eludes me (I tried using a do loop while I was trying to work out what was wrong with the second point, but I'm not convinced that the later reference to $? will be correct after a loop). So, all I can say for certain is that my patch removes the error message.

/me pines for bug-tracking software that makes it easy to attach patches.

Change History (3)

comment:1 by archaic@…, 18 years ago

(iii) the sed to format NETMOUNTS is probably not doing what is intended - I have nfs mounts on /sources and /mnt/av, NETMOUNTS contains /sources /mnt/av

This will need to be fixed by mangling $IFS to make it do what you want.

/me pines for bug-tracking software that makes it easy to attach patches.

Maybe that big "Attach File" button would help. ;)

comment:2 by bdubbs@…, 18 years ago

Milestone: 6.2
Version: a-SVN

comment:3 by bdubbs@…, 18 years ago

Resolution: fixed
Status: newclosed

Fixed #1 by changing the order of the characters to \| Fixed #3 by changing the sed to /bin/sed ':a;$!N;s/\n/ /;ta' which will put the mounts on one line space separated.

Fixed #2 by fixing #2 and changing:

fuser -m -SIGTERM $NETMOUNTS

to

/bin/fuser -SIGTERM -km $NETMOUNTS

Note: See TracTickets for help on using tickets.