[SOLVED] network-online.target is reached too early

Hi,
I want to start a systemd service once my wireless card is correctly set up (especially the wifi channel).
I think that the network-online is what I need.
So, I added the following lines at the beginning of my service file :
[Unit]
Description=...
Wants=network-online.target
After=network-online.target
However, it seems that the network-online.target is reached really early in the boot process, far before the discovery of the wireless card.
I don't know if it's important, but my wireless network is configured with netctl-auto.
I'm not very familiar with systemd, so I don't even understand how network-online.target is supposed to be notified that the network is online.
So, any help would be apreciated.
Thanks.
PS : I hope my approximative English is understandable enough.
Last edited by PHF (2013-10-28 02:51:43)

Lone_Wolf wrote:PHF, if i understand correctly you need to be sure the wireless connection is up and configured before the hostapd daemon runs ?
Yes, exactly.
Lone_Wolf wrote:a solution to achieve this might be to write a special command to check if the connection is up and add a service for it like the NetworkManager-wait-online.service .
This special command could be simple, like grepping the output op of ip addr show <interfacename> in a loop until it has a valid ip address.
Well, that's what I started to guess, without certitude : I need to manually order a waiting service before network-online.target.
I think my problem is solved now .
Meanwhile, I have found the ExecUpPost option for my netctl profiles.
It gives me the ability to execute a command once the connection is active.
So, I should be able to use it for unlocking my waiting service.
Thanks a lot for your help.

Similar Messages

[Solved] systemd - network-online.target inactive dead

Still trying to get familiar with systemd after years with Ubuntu.
I have Crashplan installed and it's systemd service unit has the following line to wait until the network comes online.
After=network-online.target
However, this doesn't seem to be working. While trying to investigate this, I noticed that the target shows as 'inactive' and 'dead'. Not entirely sure what that means.
➜ ~ systemctl list-units --type=target --all | grep network-online
network-online.target loaded inactive dead Network is Online
Where can I go from here to make sure my Crashplan service only starts after the network is online?
Thanks.
Last edited by sajan (2015-04-21 22:18:14)

Head_on_a_Stick wrote:
Please post the output of:
systemctl status network-online.target
Do you actually have a working connection?
Well, I'm connected to the internet via Wifi by the time I get past my lightdm greeter. Not sure if systemd wants something else.
➜ ~ ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=1 ttl=54 time=21.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=54 time=74.9 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 21.433/48.185/74.938/26.753 ms
➜ ~ systemctl status network-online.target
● network-online.target - Network is Online
Loaded: loaded (/usr/lib/systemd/system/network-online.target; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd.special(7)
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
➜ ~ ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=1 ttl=54 time=19.3 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=54 time=24.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=3 ttl=54 time=19.2 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 19.243/20.992/24.429/2.435 ms
➜ ~
Last edited by sajan (2015-04-21 21:19:21)

Systemd --user and network-online.target

I am trying to set up a user timer unit to whose service should be triggered only after the network has become online. The problem is that the network.target and network-online.target are system targets and not available for the --user daemon. Is there anyway to achieve this?

I wonder if you are on the right track using --user? The man page says this option is "of little use except for debugging".

Error: target terminated too early to collect data

I want to run instruments to collect some memory information, from an iPhone running adhoc provisioning... when I launch the application from the XCode/Instrument/Object Allocation Tool, it launches the application fine on the iphone, but I get the following error message, on the instrument, hence no data is collected on the instrument.
"target terminated too early to collect data"
does anybody know whats going on..?

Hi Kulbir,
This Report is not Live to schedule the report. It is under Build phase. I need to send this report UAT(User Acceptance Test). I afraid, they may get same error, when they try to refresh the report.
- Refresh the report is one of the Test case. This Test case should pass without any error.
Aswell, for your question: I am applying Sum function for the reocords at Universe Level. Not at the Report Level. I have not used any report level Variables.

Windows TCP Socket Buffer Hitting Plateau Too Early

Note: This is a repost of a ServerFault Question edited over the course of a few days, originally here: http://serverfault.com/questions/608060/windows-tcp-window-scaling-hitting-plateau-too-early
Scenario: We have a number of Windows clients regularly uploading large files (FTP/SVN/HTTP PUT/SCP) to Linux servers that are ~100-160ms away. We have 1Gbit/s synchronous bandwidth at the office and the servers are either AWS instances or physically hosted
in US DCs.
The initial report was that uploads to a new server instance were much slower than they could be. This bore out in testing and from multiple locations; clients were seeing stable 2-5Mbit/s to the host from their Windows systems.
I broke out iperf
-s on a an AWS instance and then from a Windows client in the office:
iperf
-c 1.2.3.4
[ 5] local 10.169.40.14 port 5001 connected with 1.2.3.4 port 55185
[ 5] 0.0-10.0 sec 6.55 MBytes 5.48 Mbits/sec
iperf
-w1M -c 1.2.3.4
[ 4] local 10.169.40.14 port 5001 connected with 1.2.3.4 port 55239
[ 4] 0.0-18.3 sec 196 MBytes 89.6 Mbits/sec
The latter figure can vary significantly on subsequent tests, (Vagaries of AWS) but is usually between 70 and 130Mbit/s which is more than enough for our needs. Wiresharking the session, I can see:
iperf
-c Windows SYN - Window 64kb, Scale 1 - Linux SYN, ACK: Window 14kb, Scale: 9 (*512)
iperf
-c -w1M Windows SYN - Windows 64kb, Scale 1 - Linux SYN, ACK: Window 14kb, Scale: 9
Clearly the link can sustain this high throughput, but I have to explicity set the window size to make any use of it, which most real world applications won't let me do. The TCP handshakes use the same starting points in each case, but the forced one scales
Conversely, from a Linux client on the same network a straight, iperf
-c (using the system default 85kb) gives me:
[ 5] local 10.169.40.14 port 5001 connected with 1.2.3.4 port 33263
[ 5] 0.0-10.8 sec 142 MBytes 110 Mbits/sec
Without any forcing, it scales as expected. This can't be something in the intervening hops or our local switches/routers and seems to affect Windows 7 and 8 clients alike. I've read lots of guides on auto-tuning, but these are typically about disabling scaling
altogether to work around bad terrible home networking kit.
Can anyone tell me what's happening here and give me a way of fixing it? (Preferably something I can stick in to the registry via GPO.)
Notes
The AWS Linux instance in question has the following kernel settings applied in sysctl.conf:
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.rmem_default = 1048576
net.core.wmem_default = 1048576
net.ipv4.tcp_rmem = 4096 1048576 16777216
net.ipv4.tcp_wmem = 4096 1048576 16777216
I've used dd
if=/dev/zero | nc redirecting to /dev/null at
the server end to rule out iperfand
remove any other possible bottlenecks, but the results are much the same. Tests with ncftp(Cygwin,
Native Windows, Linux) scale in much the same way as the above iperf tests on their respective platforms.
First fix attempts.
Enabling CTCP - This makes no difference; window scaling is identical. (If I understand this correctly, this setting increases the rate at which the congestion window is enlarged rather than the maximum size it can reach)
Enabling TCP timestamps. - No change here either.
Nagle's algorithm - That makes sense and at least it means I can probably ignore that particular blips in the graph as any indication of the problem.
pcap files: Zip file available here: https://www.dropbox.com/s/104qdysmk01lnf6/iperf-pcaps-10s-Win%2BLinux-2014-06-30.zip (Anonymised
with bittwiste, extracts to ~150MB as there's one from each OS client for comparison)
Second fix attempts.
I've enabled ctcp and disabled chimney offloading: TCP Global Parameters
Receive-Side Scaling State : enabled
Chimney Offload State : disabled
NetDMA State : enabled
Direct Cache Acess (DCA) : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : ctcp
ECN Capability : disabled
RFC 1323 Timestamps : enabled
Initial RTO : 3000
Non Sack Rtt Resiliency : disabled
But sadly, no change in the throughput.
I do have a cause/effect question here, though: The graphs are of the RWIN value set in the server's ACKs to the client. With Windows clients, am I right in thinking that Linux isn't scaling this value beyond that low point because the client's limited CWIN
prevents even that buffer from being filled? Could there be some other reason that Linux is artificially limiting the RWIN?
Note: I've tried turning on ECN for the hell of it; but no change, there.
Third fix attempts.
No change following disabling heuristics and RWIN autotuning. Have updated the Intel network drivers to the latest (12.10.28.0) with software that exposes functioanlity tweaks viadevice manager tabs. The card is an 82579V Chipset on-board NIC - (I'm going to
do some more testing from clients with realtek or other vendors)
Focusing on the NIC for a moment, I've tried the following (Mostly just ruling out unlikely culprits):
Increase receive buffers to 2k from 256 and transmit buffers to 2k from 512 (Both now at maximum) - No change
Disabled all IP/TCP/UDP checksum offloading. - No change.
Disabled Large Send Offload - Nada.
Turned off IPv6, QoS scheduling - Nowt.
Further investigation
Trying to eliminate the Linux server side, I started up a Server 2012R2 instance and repeated the tests using iperf (cygwin
binary) and NTttcp.
With iperf,
I had to explicitly specify -w1m on both sides
before the connection would scale beyond ~5Mbit/s. (Incidentally, I could be checked and the BDP of ~5Mbits at 91ms latency is almost precisely 64kb. Spot the limit...)
The ntttcp binaries showed now such limitation. Using ntttcpr
-m 1,0,1.2.3.5 on the server and ntttcp
-s -m 1,0,1.2.3.5 -t 10 on the client, I can see much better throughput:
Copyright Version 5.28
Network activity progressing...
Thread Time(s) Throughput(KB/s) Avg B / Compl
====== ======= ================ =============
0 9.990 8155.355 65536.000
##### Totals: #####
Bytes(MEG) realtime(s) Avg Frame Size Throughput(MB/s)
================ =========== ============== ================
79.562500 10.001 1442.556 7.955
Throughput(Buffers/s) Cycles/Byte Buffers
===================== =========== =============
127.287 308.256 1273.000
DPCs(count/s) Pkts(num/DPC) Intr(count/s) Pkts(num/intr)
============= ============= =============== ==============
1868.713 0.785 9336.366 0.157
Packets Sent Packets Received Retransmits Errors Avg. CPU %
============ ================ =========== ====== ==========
57833 14664 0 0 9.476
8MB/s puts it up at the levels I was getting with explicitly large windows in iperf.
Oddly, though, 80MB in 1273 buffers = a 64kB buffer again. A further wireshark shows a good, variable RWIN coming back from the server (Scale factor 256) that the client seems to fulfil; so perhaps ntttcp is misreporting the send window.
Further PCAP files have been provided, here:https://www.dropbox.com/s/dtlvy1vi46x75it/iperf%2Bntttcp%2Bftp-pcaps-2014-07-03.zip
Two more iperfs,
both from Windows to the same Linux server as before (1.2.3.4): One with a 128k Socket size and default 64k window (restricts to ~5Mbit/s again) and one with a 1MB send window and default 8kb socket size. (scales higher)
One ntttcp trace
from the same Windows client to a Server 2012R2 EC2 instance (1.2.3.5). here, the throughput scales well. Note: NTttcp does something odd on port 6001 before it opens the test connection. Not sure what's happening there.
One FTP data trace, uploading 20MB of /dev/urandom to
a near identical linux host (1.2.3.6) using Cygwin ncftp.
Again the limit is there. The pattern is much the same using Windows Filezilla.
Changing the iperf buffer
length does make the expected difference to the time sequence graph (much more vertical sections), but the actual throughput is unchanged.
So we have a final question through all of this: Where is this limitation creeping in? If we simply have user-space software not written to take advantage of Long Fat Networks, can anything be done in the OS to improve the situation?

Hi,
Thanks for posting in Microsoft TechNet forums.
I will try to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Kate Li
TechNet Community Support

TS4.2: VI too early to convert

Hi,
I'm getting the error -18002 VI too early to convert when I execute a TestStand 4.2 sequence file with the TestStand Base Deployment Engine. I created the Deployment installer with the deployment tool in TS4.2 and installed it on a second system. I added all needed LV runtimes and drivers incl. TestStand Deployment Engine. All installed softwares shown in the MAX are equal to the Developing system. But on the target system I always get the mentioned error. So I searched the NI Forum and found a similar Problem, but no real solution for that. I think, that the TestStand Base Deployment Engine on the target system chooses the wrong LV runtime engine, something higher then 8.2.1 (this is the version of the VI's). When I change the Labview adapter the the developing system to 8.6.1, I get the same error. But with 8.2.1, everything works fine.
How can I change the default LabView Runtime Version for the TestStand Base Deployment Engine?
Thnaks in Advanced
M. Tiedje
Solved!
Go to Solution.

mtimti wrote:
[...]I need a something like the LabView Adapter (like in TestStand developing system) in the TestStand Base Deployment System.[...]
The TestStand deployment has also settings for Adapters. It is possible, that your UI does not supply you with the option to change those settings. You can always install the predefined UIs delievered with TestStand and run it on the deployment system. You can then change the settings for the LV Adapter as needed.
mtimti wrote:
[...]All my settings and software version are identical on both systems.[...]
If this is true, then the LV Adapter settings should already be correct. Therefore, there has to be another reason for this behavior. But please check the settings as described before.
mtimti wrote:
[...]The whole problem started when we decided to change the TS version form 3.5 to 4.2. everything was fine with 3.5 and I thought I only need to deploy everything again and that's it, bau then came the VI version error.[...]
Never heared something like this. I asume that not only TestStand was updated in the process. Is it possible, that you have been working with something older than LV 8.2 when using TS 3.5? If so, please masscompile all VIs using 8.2 before deploying them.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Invalid Credentials: The Network location cannot be reached

I am working with MDT 2010, and I am getting the error, "Invalid Credentials: The Network location cannot be reached." When I run the LiteTouch 64 bit, I don't think the network is working. It's like there is not driver for the network card in
the LiteTouch 64 bit to make the network connection. When I hit F8 key, it brings a DOS box up for testing, and I found out these things.
- I can ping the loop back address 127.0.0.1.
- Cannot use the net use command to connect to the server share \\server01\DeploymentSahre$.
- I can not ping by name or IP address the server that is holding my Deployment Share.
This is the first time I am working with this technology, and I was following a guide off the Technet library. It almost like I am missing the driver for the network card. I have Windows Deployment installed on server01, the server will answer,
and I am able to put in my user name and password, it accepts and starts loading.
I did figure out how to inject the network drivers into Windows Deployment for the Motherboard I was using, do I have to do the same thing here again? MDT is using the Windows Deployment Images on the server01; MDT is setup on server01. I would have
thought that since the driver was already injected into the Image MDT would use that as well. So, do I need to put a driver into the LiteTouch 64bit image and if I do how do I do that?
thanks very much for your help,
Rick Arnold
ArnoldConsult
Rick Arnold Arnoldconsult, MCP

If you haven't updated the deployment share after adding the proper drivers to OOBD then your LiteTouch boot images will not have them included. Just right click the deployment share and click on Update Deployment Share, it will take a while but it
will rebuild the boot images with the drivers you've included in OOBD. Then it's just a matter of either recreating the flash drives or loading the updated image into WDS.
Another thought:
We had an issue with some HP's that had Main Boards replaced. the BIOS time was WAY off and the UUID wasn't setting itself because the network was denying it access to our servers (because of the horribly wrong time). Once we corrected the time
in the BIOS everything ran fine. The error we got while trying to do the deployment was the same as what you describe and we could still ping various machines on the network too.

Material Cost Estimate - Release too early

Hi,
I ran the cost estimate for one material on 12.06.2008 and i released the cost estimate. Here it is saying 'Cost Estimate released too early'. I thought system is releasing the cost for material for the next month. but i want to update the material cost for this month only.
And how many days before you have to run the cost estimate for the new month.
sateesh

Hi Sateesh,
Please check the period which you have mentioned in CK24.
I think the period you have given is of next month. Hence system is giving that message as next month's period may not have been opened.
System allows to release cost estimate only once in a period. Normal practice is to carry out cost run at the end of the month.
Please do let me know if your problem is solved.
regards,
makrand

Is it too early to start with JavaFX Mobile Development ?

There are no developer compnents except "TextBox"
The only samples i can see are "showing Photos in grid like structure & similar kinds of app" :(
it doesn't even support Swing
What developer wants "Data Entry Form" which user will submit data to Server Or Store data To Database & then Process the Data & return Result to user, Etc & much more req
why javaFx is more Media Oriented( Audio, Video,Graphics,Animation,Games,etc)
What benifits it provides to Developer.I am basically targetting JavaFX Mobile
Please Reply to help me understand What Can I do In JavaFx mobile domain
Thanks & Regards,
Pravin

Hello, and Welcome to the HP Support Community! As with any Internet Forum, you have to realize that you are visiting a "hospital" - most folks here are the minority who have had problems. If one was to judge the human race by visiting a hospital, you might run outside screaming "WE'RE ALL DOOMED! EVERYONE HERE IS SICK!!!" Those who have no issues at all do not come here and check in. The few that actually do come by and offer compliments are far and few between, and they are greatly appreciated by us! I've asked HP about Win10. They will not provide an answer until the final release is out. It could run with zero issues, or not! The Sprout is an amazing device - a large touchscreen All In One computer with some cool options not many other PC's could ever do! Is it too early? I've had one for almost a year (a loaner from HP for my participation here). Glitches? A few that were easily remedied. The decision is up to you. If worried about Win10, then wait a month or two. The device runs fine on Win 8.1. Why change to Win10? WyreNut

Reg reboot issue - console message- svc:/network/iscsi/target:default: Method or service exit timed out

Hi,
When I reboot the system I am seeing this message on the console and system is not getting rebooted.
svc.startd[10]: svc:/network/iscsi/target:default: Method or service exit timed out. Killing contract 131.
can someone help me to solve this?

There are still a few issues with Solaris 11.1 and iSCSI LUN and rebooting. I know they are working on fixes.
A possible workaround is to use the reboot command and NOT the init command. At least when you use the reboot the command the system will reboot and not hang.
If this is not your problem then it may be a different problem.
Andrew

GCU membership set to expire 11 months too early

Hello! I'm posting here about an issue with my Gamer's Club Unlocked membership. These snippets of my emails to Best Buy Customer Support should explain my problem:
12/19/2013
Me: I just renewed my Best Buy GCU membership for an additional two years, but my problem is that those two years did not stack with the remaining time on my previous one year membership, which did not expire until February 10, 2014. My newly-renewed membership says it will expire on December 18, 2015, but it should not expire until February 10, 2016. Will you please fix this?
Date unknown
Me: I renewed my GCU membership last December, but I haven't received the physical magazine in the mail since then, nor have I ever received any of the digital version's coupons.
02/25/2014
Support: I suggest you to go at the store and they will be more than glad to assist you with your concern.
Date unknown
Me: I already tried asking the store manager at my nearest Best Buy for help with this multiple times. She said there was nothing she could do, and to contact online customer support. You're the third online customer support Rep to suggest I go back to the store for help. I'm tired of getting bounced back and forth...
02/27/2014
Support: We are experiencing system maintenance, reason why it is reflecting that date. As soon as it is over, the correct date will be reflected on your account.
Date unknown
Me: It's now been about a week and a half since your most recent reply, and my Gamer's Club Unlocked memberships is still set to expire on December 18, 2015, when it should not expire until February 10, 2016. Surely "system maintenance" wouldn't be going on this long... I asked the store manager of my nearest Best Buy one more time if she could help with this -- once again, she said no. Will this ever get fixed? Or am I just stuck with losing two months of my membership?
03/11/2014
Support: In regard to your concern, we were having system maintenance issue however, you will not loose two months of your membership it will expired the date it should be.
03/12/2014
Me: I just checked my account, and now my Gamer's Club Unlocked membership is set to expire on 3/10/2015. It's even worse now than it was before! Now it's set to expire 11 months too early. My GCU membership should not expire until 02/10/2016.
03/12/2014
Support: We have escalate this case to our support department. This process will take 7 to 10 business day and they will contact you with a resolution to your concern.
Nearly 4 months later, I have not received any further messages from Customer Support, and my GCU membership is still set to expire 11 months too early. Would someone here please help me with this?

Hey Bent_00,
As enuf mentioned, your patience is absolutely incredible and I sincerely thank you for it. It’s clear to me that you’ve spent a significant amount of time working with our support representatives in regards to your Gamers Club Unlocked (GCU) membership expiration date. While I greatly thank you for joining GCU, I do apologize for any confusion you’ve endured about when your benefits should expire.
This is in fact a known issue and our My Best Buy team has been working to resolve the issues causing your expiration date to reflect incorrectly. While some GCU members are now seeing their correct expiration date, we are aware that some may still be incorrectly reflecting. As enuf further alluded to, we are very confident that this will be resolved well before your GCU benefits would ever expire.
I appreciate you sharing your concerns with us on the forums. If you have any other questions, please don’t hesitate to ask! Thanks again for being a GCU member.
Best regards,
Brian|Senior Social Media Specialist | Best Buy® Corporate
Private Message

Lvwutil32 version too early to covert to current LabVIEW version?

Hi all,
I am looking to control the windows panel with some of the useful vis stored inside the lvwutil32 lib. However when I tried to open the vis inside the library, an error message saying that the vi version (4.0) is too early to be converted to my current LabVIEW version (8.5.1).
Is there anyway to reconvert the vi that my current LabVIEW can use? It is a great shame as from the readme that comes with the lvwutil32, it seems that there are a lot of useful vis that I would find very useful for my projects.
Hope someone could provide some help on this. Thanks!
Solved!
Go to Solution.

                       Hello,
                       I am having the same problem as YuanGe(the topic owner). I wanna open a file from the 5.1.1 LABview version on my LABview 8.6 and occurs the same error message.
                      I would be very grateful, if anybody could help me.
                      Thanks.
                      ps: The file is just down here.
Attachments:
ag8614x.zip ‏2795 KB

Systemd: some services starting too early and then failing

Hello everyone,
I freshly installed Arch on this new laptop (Asus Zenbook Prime UX32VD) and from the start, I wanted to have a pure systemd setup. I'm using services only and I've uninstalled initscripts and so far it's working relatively well.
However, some services seem to start too early by default and the workarounds are unsatisfactory.
Problem 1: asus-screen-brightness and asus-kbd-backlight
On this lap top, the stock screen brightness buttons do not work (yet). A script and a service file (which are both available via the asus-screen-brightness AUR package) have to be used to allow users to change the brightness via the script. The problem is, with that service enabled, it only succeeds sometimes. About have of the time booting the laptop it fails, most likely because the necessary nodes in /sys/ do not exist yet. Restarting the service manually after booting does the trick:
[root@tachychineta shapeshifter]# sc status asus-screen-brightness
asus-screen-brightness.service - Allow user access to screen brightness
Loaded: loaded (/etc/systemd/system/asus-screen-brightness.service; enabled)
Active: active (exited) since Fri, 12 Oct 2012 11:23:44 +0200; 1min 1s ago
Process: 320 ExecStart=/usr/bin/asus-screen-brightness allowusers (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/asus-screen-brightness.service
Oct 12 11:23:44 tachychineta systemd[1]: Starting Allow user access to screen brightness...
Oct 12 11:23:44 tachychineta sudo[349]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod g+w /sys/class/backlight/intel_backlight/brightness
Oct 12 11:23:44 tachychineta sudo[349]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: cat: /sys/class/backlight/intel_backlight/max_brightness: No such file or directory
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: /usr/bin/asus-screen-brightness: line 8: /10: syntax error: operand expected (error token is "/10")
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: /usr/bin/asus-screen-brightness: line 10: 2*: syntax error: operand expected (error token is "*")
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: cat: /sys/class/backlight/intel_backlight/brightness: No such file or directory
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: chgrp: cannot access ‘/sys/class/backlight/intel_backlight/brightness’: No such file or directory
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: chmod: cannot access ‘/sys/class/backlight/intel_backlight/brightness’: No such file or directory
Oct 12 11:23:44 tachychineta systemd[1]: Started Allow user access to screen brightness.
[root@tachychineta shapeshifter]# sc restart asus-screen-brightness
[root@tachychineta shapeshifter]# sc status asus-screen-brightness
asus-screen-brightness.service - Allow user access to screen brightness
Loaded: loaded (/etc/systemd/system/asus-screen-brightness.service; enabled)
Active: active (exited) since Fri, 12 Oct 2012 11:25:28 +0200; 2s ago
Process: 2547 ExecStop=/usr/bin/asus-screen-brightness disallowusers (code=exited, status=0/SUCCESS)
Process: 2579 ExecStart=/usr/bin/asus-screen-brightness allowusers (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/asus-screen-brightness.service
Oct 12 11:25:28 tachychineta systemd[1]: Starting Allow user access to screen brightness...
Oct 12 11:25:28 tachychineta sudo[2593]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/chgrp users /sys/class/backlight/intel_backlight/brightness
Oct 12 11:25:28 tachychineta sudo[2593]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 12 11:25:28 tachychineta sudo[2597]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod g+w /sys/class/backlight/intel_backlight/brightness
Oct 12 11:25:28 tachychineta sudo[2597]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 12 11:25:28 tachychineta systemd[1]: Started Allow user access to screen brightness.
Exactly the same problem occurs with asus-kbd-backlight.service which is needed to allow users to control the keyboard backlight. It also fails because of missing /sys/ entries if started too early.
Problem 2: automatic login & X11
I use the method described on the wiki to autologin into TTY1 with my user and my .bash_profile contains
[[ $(fgconsole) = 1 ]] && startx
and my .xserverrc is configured as explained in this fantastically useful article by falconindy.
This way, X starts automatically and my session is properly authenticated for things like udiskie. I'm not using [testing] but instead rebuilt polkit with --enable-systemd and it's working just fine. The problem is, just like in problem 1, Xorg fails to start every now and then, failing with
(EE) No devices detected.
I don't have a full log because it hasn't happened in a while, but I'm very certain it's because the chipset isn't ready, yet.
Solutions?
I added "i915" to /etc/modules-load.d/static.conf hoping that would cover both the Xorg and backlight problems but it doesn't help. I then tried adding i915 to my MODULES in mkinitcpio.conf and rebuilding the initramfs and at least it looked like that way the problems went away but it added about 4 seconds to the time spent by the "kernel" during boot which is quite unacceptable. (Plots with and without i915 in MODULES).
I read the systemd.unit and systemd.service man pages but I can't find a way to speficy required kernel modules for a service file. I'm not sure if specifying the modules in /etc/modules-load.d shouldn't be enough (because apparently it's supposed to load for sysinit.target, which is early) but apparently it isn't.
Any ideas how I can get these services to work properly without sacrificing too much boot time?
Thank you
Last edited by Shapeshifter (2012-10-12 10:20:09)

Please fill a bug report.

[Calender] Dates are misplaced a day too early

Ez all crew,
since updating to 4.0.1 my iPhone 3GS 32 GB Calender seems to begun misplacing events/activities a day too early. This is only the case on the iPhones, not on my other Mac computers. They are all synced via MobileMe.
Actually it is only the case when using the Calender in List mode, not in Day or Month mode. E.g. an event/activity added to begun on Thursday 26th August is shown on the day before (i.e. Wednesday 25th). I have screen shots from the iPhone to confirm the problem, however, it is not possible for me to send the to Apple Support. I'm told to contact my local (Danish) telephone operator company. Yet, this is clearly an Apple software problem, not the local telephone company's.
I have now updates to 4.0.2 and it did not solve the problem. Please advice. Cheers!

iPhone Calender recently started to mash up the dates again. A total reset of the MobileMe Calender sync was needed to sort it out. However, once and again the while creating a new event in the iPhone Calender it does not save it. Often it is needed to re-create it 2-3 times. This does not happen on my Macbook Pro and iMac 27" computer's Calender though. It's a strictly iPhone problem apparently,

How can I get a better driver for my 1394b Hostcontroller in my Macbook pro 2010 to solve the problem, that it is too slow under Windows 7 installed with bootcamp ?

How can I get a better driver for my 1394b Hostcontroller in my Macbook pro 2010 to solve the problem, that it is too slow under Windows 7 installed with bootcamp ?
WIndows can't find a better one than the installed LSI Conformed 1394 Hostcontroller

Read and follow the Bootcamp Installation instructions that you were offered to view when you ran Bootcamp Assistant.
Run Bootcamp Assistant again and select the option to download the Bootcamp Support software. Follow the instructions. Then boot into Windows and install the Windows Support software you downloaded and saved.

[SOLVED] network-online.target is reached too early

Similar Messages

Maybe you are looking for