Systemd: Slim fails to start automatically after boot

Hi, after some update a couple of weeks ago (I don't remember exactly), slim fails to start after boot. I use systemd and just had enabled the slim.service file that is included in the package. After boot, I can login on the tty and then restart the slim.service, and everything works.
In the slim.log file it says:
Fatal server error:
no screens found
Giving up.
slim: unable to connect to X server
/usr/bin/xauth: file /var/run/slim.auth does not exist
It seems like slim is started before X, since everything works when I restart the service manually. What is causing this problem and how can I solve it?
Best regards and thanks,
Jan Oliver

oliarch ~ sudo systemd-analyze blame
2460ms net-auto-wireless.service
243ms rsyslog.service
239ms sshd.service
183ms console-kit-log-system-start.service
136ms systemd-logind.service
124ms console-kit-daemon.service
119ms systemd-udev-trigger.service
99ms systemd-sysctl.service
82ms systemd-readahead-replay.service
80ms systemd-vconsole-setup.service
63ms systemd-user-sessions.service
62ms systemd-remount-fs.service
58ms systemd-readahead-collect.service
55ms sys-kernel-debug.mount
43ms dev-sda2.swap
43ms dev-mqueue.mount
42ms dev-hugepages.mount
26ms systemd-tmpfiles-setup.service
20ms srv.mount
13ms tmp.mount
12ms systemd-udev.service
10ms boot.mount
9ms home.mount
oliarch ~ sudo journalctl --no-pager -a | grep slim
Jun 24 14:25:01 oliarch systemd[1]: slim.service: main process exited, code=exited, status=1
Jun 24 14:25:01 oliarch systemd[1]: Unit slim.service entered failed state.

Similar Messages

Systemd Issues - Failed to start MyApp daemon

Hi all,
Sorry if I'm asking a stupid question, I'm new to Arch Linux, Pi, and Python. I have a Python script I'd like to start automatically after boot so I created a myapp.service file:
[Unit]
Description=MyApp daemon
Requires=network.target
[Service]
Type=forking
ExecStart=/root/bin/myapp/initmyapp.py
ExecStop=/bin/kill $MAINPID
[Install]
WantedBy=multi-user.target
After initmyapp.py runs it calls "myapp.py &" that's why I tried type=forking. I tested "systemctl start myapp" and it looks like it's working; I can see the process running. So, I did "systemctl enable myapp" which ran without errors and then I rebooted. After reboot, however, the process is not running and "systemctl status myapp" tells me this:
myapp.service - MyApp daemon
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Wed, 1969-12-31 19:00:10 EST; 43 years and 0 months ago
Process: 102 ExecStart=/root/bin/myapp/initmyapp.py (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/myapp.service
Dec 31 19:00:09 mybox initmyapp.py[102]: '_open', req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
Dec 31 19:00:09 mybox initmyapp.py[102]: result = func(*args)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1207, in http_open
Dec 31 19:00:09 mybox initmyapp.py[102]: return self.do_open(httplib.HTTPConnection, req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open
Dec 31 19:00:10 mybox initmyapp.py[102]: raise URLError(err)
Dec 31 19:00:10 mybox initmyapp.py[102]: urllib2.URLError: <urlopen error [Errno -2] Name or service not known>
Dec 31 19:00:10 mybox systemd[1]: Failed to start MyApp daemon.
Dec 31 19:00:10 mybox systemd[1]: Unit myapp.service entered failed state
Does this mean that networking is not ready yet? Instead of Requires=network.target I also tried Requires=multi-user.target but didn't work. I have no idea what I'm doing so any suggestion would be appreciated.

Thank you for the quick response. I removed the kill part and "stop" still works. I also removed all the network includes to test it out and the background call too and after hours of trial and error I was finally able to make it work. Now I just have to figure out how to tell when the network is up. That article covers it for C (I think) but not for Python. It also seems very technical.
Anyway, thanks again for your help.

Dhcpcd does not start automatically on boot

Hi everyone,
I have just installed Arch (64 bit) and am running on a dynamic, wired connection.
I followed the Beginners' Guide and enabled the dhcpcd service during the installation so that it would start automatically on boot.
systemctl enable [email protected]
However, I currently must issue the command "dhcpcd" each boot before the internet starts to work.
Does anyone know how I can automate this process or if I need to further configure my network connection?
Thank you in advance.
Last edited by Ipozya (2012-11-15 11:29:05)

foppe wrote:
Check the output from
# systemctl status [email protected]
to debug the issue you're experiencing.
% sudo systemctl status [email protected]
[email protected] - dhcpcd on eth0
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-15 20:38:16 GMT; 27 sec ago
Process: 244 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/[email protected]/eth0
Nov 15 20:37:47 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:47 arch dhcpcd[244]: eth0: sendmsg: Cannot assign requested address
Nov 15 20:37:47 arch dhcpcd[244]: eth0: broadcasting for a lease
Nov 15 20:37:51 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:55 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:59 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:59 arch dhcpcd[244]: eth0: no IPv6 Routers available
Nov 15 20:38:16 arch dhcpcd[244]: timed out
Nov 15 20:38:16 arch systemd[1]: Failed to start dhcpcd on eth0.
Nov 15 20:38:16 arch systemd[1]: Unit [email protected] entered failed state
Dhclient did not work automatically on boot either.
Others seem to have experienced similar issues but I don't see any real solutions in any of these posts, despite being marked as solved. For example, adding "-t 120" to the dhcpcd start line in /usr/lib/systemd/system/[email protected] did not work for me.
I also tried the following but it did not work either and I had to issue "dhcpcd" before internet started working.
Install and configure wired and wireless networking
# pacman -S netcfg ifplugd
# cd /etc/network.d
# ln -s examples/ethernet-dhcp .
Make sure the WIRED_INTERFACE and WIRELESS_INTERFACE lines is uncommented
# nano /etc/conf.d/netcfg
# systemctl enable net-auto-wired.service
# pacman -S wireless_tools wpa_supplicant wpa_actiond dialog
# systemctl enable net-auto-wireless.service
https://bbs.archlinux.org/viewtopic.php?pid=1176656
https://bbs.archlinux.org/viewtopic.php?pid=1189587
https://bbs.archlinux.org/viewtopic.php?pid=1180192
Last edited by Ipozya (2012-11-15 21:08:03)

Oracle 11g XE listener does not start automatically during boot

Hi,
This happened to me recently I just wanted to share it with you.
For development I was running Standard Edition, at some point I decided to run also XE on the same server for another reasons. Everything was working fine, except that after restart of the server, the XE listener is not starting automatically. Debugging the startup script I found that this happens because of a bug in the code, which assumes that XE listener is running if it finds the word LISTENER within the processes list. I didn't found any obligation in the docs for running XE without any other databases on the same host.
In file /etc/init.d/oracle-xe, at line 556 the code is failing:
1     + status='oracle 2889 1 0 May13 ? 00:00:05 /oracle/ora112se/bin/tnslsnr LISTENER -inherit'
2     + '[' 'oracle 2889 1 0 May13 ? 00:00:05 /oracle/ora112se/bin/tnslsnr LISTENER -inherit' == '' ']'
As you can see I have another listener(the one for SE) running and because of the XE startup script found the keyword LISTENER it’s supposing that the XE LISTENER is already running.
To fix this simply change line 556 from:
1     status=`ps -ef | grep tns | grep oracle`
To:
1     status=`ps -ef | grep tns | grep oracle | grep xe`
Now XE listener is started automatically during boot.
Sve
Blog: http://sve.to
Twitter: sgyurov

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Tip regarding the "systemd[1]: Failed to start Journal Service" error

Just a tip regarding the well-known
systemd[1]: Failed to start Journal Service
error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
In this case you will see that the problem actually lies in
systemd[1]: Cannot open /etc/machine-id: No such file or directory
Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually: /usr/bin/systemd-machine-id-setup
http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.

Jristz wrote:
ackalker wrote:Sorry for necrobumping this.
Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
He already did.
Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't.

After downloading mountain lion the internet does not start automatically after start or restart but if I use diagnostics it starts is there a simpler solution

After downloading mountain lion the internet does not start automatically after start or restart but if I use diagnostics it starts is there a simpler solution?

Extensions can sometimes be the cause of problems. If the problem does not occur in Safe Mode, then you can disable your extensions one-by-one until you find out which one is causing the problem. See [[Troubleshooting extensions and themes]]

Why Portage R700-15P starts automatically after hibernation

Why TOSHIBA Portage R700-15P starts automatically after I hibernate it (or put on sleep) and close the lid?
As soon as I take hibernated laptop with closed lid in my hands to put it into bag - it starts by itself with closed lid...
Had anybody similar issue and solution for this?
Thanks

> Is there any setting for laptop or Windows 7 that does not resumes laptop from hibernate/sleep state when lid is closed?
First of all its not matter if the lid is closed or not one fact is important: notebook is set in hibernation mode and wakes up if USB mouse would be moved
Fact is that BIOS contains some Wake Up options you should check the BIOS settings like Wake Up on LAN, Wake up on keyboard etc disable these options, save the changes and check how it works

Option that SAP starts automaticly after power loss

I am using an windows/sql ECC 6.0 server. I would like option that SAP starts automaticly after power loss. Is it possible and how?

Hi
I think this not possible.
Thanks
Pankaj Kumar

Will DB start automatically after rebooting the computer?

Will DB start automatically after rebooting the computer?

user9947478 wrote:
Will DB start automatically after rebooting the computer?Yes. IF you set it up to do so. Or you have an OSs for which it is installed to automatically do so and you have not disabled it.
I assume, since it seems to be difficult for you to tell us what operating system you use, that you use some form of Windows. In which case, the answer is 'Yes, automatically set up - as seen by the Services'.
(Windows users don't seem to realize there are other OSs and therefore don't tell. They also don't realize that Windows is not an OS, but rather the marketing label for a whole families of OS Editions. Some popular families are: Windows XP, WIndows 2003, Windows 2008, Windows 7. But even then, Oracle only works on specific Editions within the family.)

[SOLVED] systemd : services failing to start on boot

I have removed sysvinit completely as per the systemd wiki pages.
I don't usually re-boot very often so I'm not sure exactly when the problem started.
I only noticed this problem about 4 or 5 days ago.
But now whenever I reboot my machine 2 services fail consistently.
adsl.service
colord.service
They both start flawlessly once I can log in at a console.
I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
I need some help and advice to find out what is causing the problem and how to fix it.
Last edited by bhrgunatha (2012-10-25 05:44:22)

Thanks. That seems plausible. So I've been snooping at the journal.
journalctl -ab
Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: peers refreshed
Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
That seems to confirm your theory.
eth0 link is not up when attempting to start colord and adsl
So the $64,000 question:
How do I defer them until eth0 is ready?
Or how can I force the eth0 link to be up before colord or adsl try to use it?
Last edited by bhrgunatha (2012-10-25 01:33:36)

PC Suite not starting automatically after re-boot.

Running the latest version of PC Suite in 32bit Vista. Every time I re-boot my PC, PC Suite refuses to start automatically, and there is no icon in the tray. I have to go into start, programs, etc..,then 'click to connect a phone' every time. Very annoying!
Very strange behaviour, given the fact that my laptop (running XP Pro), starts up with PC suite in the tray and connects with my phone via bluetooth without any intervention whatsoever.
Anyone experienced or solved this problem?
Jimmy.

In the start up tab of system config, there is no 'launch application' listed. However, PC suite is listed and enabled.
An update on this problem: Having looked at various previous posts, it would appear that ATI Catalyst Control Centre conflicts with the start-up of PC Suite. I have uninstalled this app, and all would now seem to be well. I beleive ATI CCC causes quite a few problems with Nokia software judging by problems other posters are having..
Jimmy.

Listener service not start automatically after reboot in Win2K server Clust

Hi all,
I set up a two node Server Cluster with Microsoft Windows 2000 server cluster service. Hardware are two HP DL380 servers and HP MSA500 (the shared storage). The cluster's IP address is 10.1.241.65. When I shut down both servers and restart the primary server, the listener server service will not start automatically. The listener log is:
Started with pid=1108
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.1.241.65)(PORT=1521)))
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
32-bit Windows Error: 49: Unknown error
The service is set up automatically start. I suspect the cluster virtual IP is not available immediately after reboot. So I tried setting the Recovery after first failure and second failure to 3 minitues each, and setting up Dependencies of the listener on the cluster service in the Win2K Service panel. Neither worked.
The service can be manually start.
Any suggestion?
Frank.

The command to start automatically the listener is :
lsnrctl start
check the parameters in : <ORACLE_HOME>/network/admin/listener.ora
check the IP address or host name
Joel Pérez

Noip2 can't get my IP when run automatically after booting

I'm trying to set up a VPN and I use the noip.com service. I use the "noip" package to update my hosts.
If I run it manually with systemctl start noip2, it works fine and my host is updated properly.
If I set it to be run after booting with systemctl enable noip2, it doesn't work and gets caught in an endless loop that looks like this:
Mar 28 19:44:07 eee systemd[1]: Started No-IP Dynamic DNS Update Client.
Mar 28 19:44:07 eee noip2[154]: v2.1.9 daemon started with NAT enabled
Mar 28 19:44:07 eee noip2[154]: Can't gethostbyname for dynupdate.no-ip.com
Mar 28 19:44:07 eee noip2[154]: Can't get our visible IP address from ip1.dynupdate.no-ip.com
Mar 28 19:49:07 eee noip2[154]: Can't gethostbyname for dynupdate.no-ip.com
Mar 28 19:49:07 eee noip2[154]: Can't get our visible IP address from ip1.dynupdate.no-ip.com
I suspect this is because the network isn't ready by the time the noip2 service is launched, so it can't resolve the updater domain name. However, I don't understand why, after five minutes, it still can't resolve this domain name. I can ping it just fine.
Any ideas are more than welcome

Okay, so how are you starting your internets? Is it with a wired conenction, or wireless? Netcfg, dhcpcd, NetworkManager, wicd, do you send carrier pidgeons back and forth?
If it requires that you have an active connection when it starts, maybe you should try using NetworkManager's service that waits until it is online before it notifies (creatively named NetworkManager-wait-online.service). I think that what this does is it delays the completion of the network.target until after this service starts. So if you have noip.service be "After=network.target" then the IP should be resolved and ready to go.

Hyper-V - virtual machines don't start automatically after power outage

Hi,
I have a HP server running Windows 2012 R2 + Hyper-V. On this server, four VM have Windows Server 2003 R2, and one VM has Windows 2012. After power outage, 1 2003 R2 VM and 1 2012 VM are started properly, but the other three machines aren't. I've started
it manually. All VM's have last version of Hyper-V integration tools installed, the option "Automatically start VM if it was running before the service was stopped" was chosen. I'm not very familiar with Hyper-V, so, I've investigated only Hyper-V-VMMS
event log. There are some recurring errors:
The Integration Services Setup Disk image could not be updated: The process cannot access the file because it is being used by another process. (0x80070020).
and
Failed to get the disk information.
But I think it isn't a clue.
How can I clarify, why these machines aren't started automatically?

Hi EugenBerend,
Maybe it is related to system resources allocation during the start up .
I would suggest you to configure a startup delay for those lower priority machines so that system
can locate enough resource for them.
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

J2EE process in SAPMMC do not start automatically after a restart

Hello All,
I have a Netweaver with only J2EE engine set up.
Whenever I restart the server, the services at SAPMMC->Console Root-> SAP Systems-> Instance-> Process List,Current Status, Open Alerts, J2EE Process Table do not start automatically.
I have to start them manually.
Please let me know what configuration I need to make them automatic.
Thanks
Raman

Hi,
Please confirm that J2ee is failing to start when you restart the server. If yes do post the logs so that we can drill to the max extent.
Rgds
Radhakrishna D S
Edited by: Radhakrishna D S on Sep 8, 2008 8:17 AM
Edited by: Radhakrishna D S on Sep 8, 2008 8:18 AM
Edited by: Radhakrishna D S on Sep 8, 2008 8:19 AM

Systemd: Slim fails to start automatically after boot

Similar Messages

Maybe you are looking for