Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25587 - [netcfg] 2.6.8 git version of 11netcfg always starts all netcfg daemons after resume from standby

Attached to Project: Arch Linux
Opened by Oleksii Tkachuk (alexta) - Monday, 15 August 2011, 17:47 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 20 March 2012, 23:24 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

It is known that original 11netcfg hook from pm-utils package doesn't work with netcfg daemons: net-profiles, net-auto-wired and net-auto-wireless. This problem can be solved partly by using 11netcfg from netcfg git. But there are following problems in it:

1. pmfunctions stopservice and restartservice are used to run/stop daemons. Actually these two functions should consider the current state of a daemon: function restartservice starts some daemon only in the case if a daemon was running and was stopped by stopservice function before. But there is a bug in stopservice function and it considers that any existent daemon is running now. As a result, after a resume from standby all netcfg daemons are started and it doesn't depend on their condition before suspend.

2. 11netcfg from git works only in binary mode: whether with daemons, or with manually started profiles (environment variable NETCFG_SUSPEND is responsible for this). I'm not a guru in netcfg, but I think that behavior for both variants can be combined, if correct sequence of run/stop of demons and suspend of manual profiles are used.

There is a patch in attach that fixes first issue and may fix the second.

P.S. I also have a minor patch for a file /usr/lib/pm-utils/bin/service from pm-utils package, which is responsible for the error in the stopservice function. But this is upstream bug and last changing of pm-utils git was done 9 month ago... Could someone from community say me, where I can upload a patch for its faster implementation in pm-utils?
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 20 March 2012, 23:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  netcfg 2.7.1-1
Comment by Leonid Isaev (lisaev) - Monday, 22 August 2011, 17:55 GMT
Hmm, what do you mean by does not work? For me, net-profiles suspend and resume correctly with 2.6.7...
Comment by Oleksii Tkachuk (alexta) - Wednesday, 24 August 2011, 21:12 GMT
If you mean original 11netcfg from pm_utils, it works only with active profiles and knows nothing about auto daemons (I consider net-profiles to be auto daemon too, because you can use it not only during boot; restart of this daemon will cause сonsistence enumeration of specified profiles).

Thus, original 11netcfg saves all ACTIVE profiles by calling "netcfg all-suspend" before suspend. After resume this script tries to reconnect saved profiles by calling "netcfg all-resume". Another NOT SAVED profiles will not be tried at all.

If you work in various environments with different profiles this is not your way (it will no automatic profiles switching).

Loading...