Ich weiß nicht mehr weiter. Habe nun ein Hook namens 90_wakeserver
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16 | ls -l /usr/lib/pm-utils/sleep.d/
total 72
-rwxr-xr-x 1 root root 292 2011-04-30 21:27 000kernel-change
-rwxr-xr-x 1 root root 274 2011-04-30 21:27 00logging
-rwxr-xr-x 1 root root 203 2011-04-30 21:27 00powersave
-rwxr-xr-x 1 root root 886 2011-04-30 21:27 49bluetooth
-rwxr-xr-x 1 root root 1228 2011-04-30 21:27 55NetworkManager
-rwxr-xr-x 1 root root 453 2011-04-30 21:27 75modules
-rwxr-xr-x 1 root root 614 2011-04-30 21:27 90clock
-rwxr-xr-x 1 root root 87 2011-09-21 13:36 90_wakeserver
-rwxr-xr-x 1 root root 1098 2011-04-30 21:27 94cpufreq
-rwxr-xr-x 1 root root 732 2010-03-05 03:31 95anacron
-rwxr-xr-x 1 root root 297 2011-04-30 21:27 95led
-rwxr-xr-x 1 root root 707 2010-11-19 18:33 95packagekit
-rwxr-xr-x 1 root root 13893 2011-04-30 21:27 98video-quirk-db-handler
-rwxr-xr-x 1 root root 5667 2011-04-30 21:27 99video
|
mit folgendem Inhalt erstellt:
| #!/bin/sh
case "$1" in
resume|thaw)
/usr/local/sbin/wakeserver.sh
;;
esac
exit $?
|
Dennoch bekomm ich meine Laptop nicht dazu meinen Server zu wecken. Was mach ich falsch?
EDIT1/2:
Lösung doch noch nicht gefunden!
Die Hooks werden priorisiert (nach einander ausgeführt). Bisher lief das Hook mit der fast höchsten Priorität (90). Das hat zur Folge, dass das Magic-Packet abgeschickt wird, noch bevor der Network-manager (Priorität 55) gestartet ist. Durch ändern der Priorität (50) wird das Paket nun gesendet nachdem der Network-manager gestartet wurde.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64 | Wed Sep 21 14:07:22 CEST 2011: Awake.
Wed Sep 21 14:07:22 CEST 2011: Running hooks for resume
Running hook /etc/pm/sleep.d/action_wpa resume suspend:
/etc/pm/sleep.d/action_wpa resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95packagekit resume suspend:
method return sender=:1.272 -> dest=:1.326 reply_serial=2
/usr/lib/pm-utils/sleep.d/95packagekit resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95anacron resume suspend:
/usr/lib/pm-utils/sleep.d/95anacron resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up...method return sender=:1.2 -> dest=:1.327 reply_serial=2
Done.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/50_wakeserver resume suspend:
SIOCGIFHWADDR on eth0 failed: No such device
/usr/lib/pm-utils/sleep.d/50_wakeserver resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
Running hook /etc/pm/sleep.d/10_unattended-upgrades-hibernate resume suspend:
/etc/pm/sleep.d/10_unattended-upgrades-hibernate resume suspend: success.
Running hook /etc/pm/sleep.d/10_grub-common resume suspend:
/etc/pm/sleep.d/10_grub-common resume suspend: success.
Running hook /etc/pm/sleep.d/01mbm resume suspend:
PIN = PUK =
Error org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch daemon, file not found or permissions invalid
/etc/pm/sleep.d/01mbm resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/000kernel-change resume suspend:
/usr/lib/pm-utils/sleep.d/000kernel-change resume suspend: success.
Wed Sep 21 14:07:33 CEST 2011: Finished.
|
Dennoch funktioniert das aufwecken noch nicht zuverlässig.
Kann jmd. dieses Verhalten bestätigen?
EDIT3
Die Zuverlässigkeit lässt sich erhöhen, in dem man einen ausreichend großen sleep einbaut. Kaskadiert schaut das bei mir so aus:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27 | #!/bin/bash
INTERFACE="eth6"
MAC="xx:xx:xx:xx:xx:xx"
etherwake -i "$INTERFACE" "$MAC"
#!/bin/bash
INTERFACE="wlan0"
MAC="xx:xx:xx:xx:xx:xx"
etherwake -i "$INTERFACE" "$MAC"
#!/bin/bash
INTERFACE="wlan0"
MAC="xx:xx:xx:xx:xx:xx"
sleep 5
etherwake -i "$INTERFACE" "$MAC"
#!/bin/bash
INTERFACE="wlan0"
MAC="xx:xx:xx:xx:xx:xx"
sleep 5
etherwake -i "$INTERFACE" "$MAC"
#!/bin/bash
INTERFACE="wlan0"
MAC="xx:xx:xx:xx:xx:xx"
sleep 10
etherwake -i "$INTERFACE" "$MAC"
|
.. ob das alle Tage Abend ist, kann ich jedoch nicht sagen.
EDIT4:
Die Aktuelle Konfiguration funktioniert bisher problemlos 😉
→ closed
LG H.i.M