Process start at boot time..

Hi All,
I am developing a client application which needs to be start up at boot time and there is one more requirement that no body
should be able to delete this to provide it security.
Please reply .
Thanks

Hi,
Processes, are not able to start at boot-time as the "processes" is a OS based concept. The closest method you can do is replace the bootloader of Windows with your bootloader then load the Windows through your bootloader, and before loading the OS your
Bootloader can perform any calculations or start files up as soon as Windows loads. This is the only way to start processes closest to Boot time.
In windows vista+ OS this technique would not work because Windows Vista+ has Session separation which by design separates processes into sessions and if you were to start it as soon as the OS starts the process would crash the entire OS as the process would
not be able to fit in any session as it started before "Winlogon.exe"
process. Therefore it is not really possible.

Similar Messages

Auditing a process started at boot time

Hi All,
I am having a problem with auditd. I am starting a process of my own at boottime that I would like to audit. I think the problem lies in that my process is not getting an auditID. If I run the process from a terminal after the system is started it audits correctly, only when started at boot will it not audit.
I have the process's audit class defined in the audit_control file as such (md is my audit class):
dir:/var/audit
flags:md,lo,ad,-fw,-fm,-fd,-nt,no
minfree:50
naflags:md
I thought placing it under naflags would allow it to audit without attributes, but this does not work. The audit event and audit class are also properly in place.
Any help with getting a process to audit when started at boot would be greatly appreciated.
Victor

Hi,
Processes, are not able to start at boot-time as the "processes" is a OS based concept. The closest method you can do is replace the bootloader of Windows with your bootloader then load the Windows through your bootloader, and before loading the OS your
Bootloader can perform any calculations or start files up as soon as Windows loads. This is the only way to start processes closest to Boot time.
In windows vista+ OS this technique would not work because Windows Vista+ has Session separation which by design separates processes into sessions and if you were to start it as soon as the OS starts the process would crash the entire OS as the process would
not be able to fit in any session as it started before "Winlogon.exe"
process. Therefore it is not really possible.

SMF - start at boot time, but don't restart - possible?

I'm setting up a software package that has a number of background processes.
I've got SMF manifests created and imported for all of them, and they're working great for starting the processes at boot time, and doing the automatic restarts when one fails.
Here's my problem. It turns out that the users of this software want to be able to use the software's integrated process control methods to stop some of their processes. With the current configuration, they use the software's method to stop one of it's processes, and SMF promptly restarts it.
Is there a way to set up SMF managed software so that SMF starts it at boot time, but then doesn't care if stops later?
Richard

I'm not sure how it would be SMF "managed" in such a case. Obviously you want the management to be elsewhere.
You could use the "legacy" startup scripts in /etc/rcX.d. That will start a process and forget about it, just like pre-Solaris 10. You don't use manifests or have any other benefits of SMF.
If you do want SMF, I guess the question is how you want it to act..
When the users stop the processes, do you want SMF to say enabled or disabled? SMF does not track enabled processes by periodic polling, it does it by tracking contracts. This means that starting a process outside of SMF does not allow SMF to track it.
Darren

[SOLVED] rtorrent&screen don't start at boot time

Hello. I use rc-script from ArchWiki to start screen with rtorrent (http://wiki.archlinux.org/index.php/RTo … ith_screen), but at boot time neither rtorrent nor screen start, although script prints "[DONE]". If I login as root and start script manually it works perfect, but I can't understand why it doesn't start automatically.
Please, help.
P.S. Of course script was added to DAEMONS array in rc.conf.
Last edited by Atragor (2009-03-29 11:56:10)

jordz, adding command to rc.local didn't change anything.
LeoSolaris, yes, script is executable, and according to screen's man page:
-d -m Start screen in "detached" mode. This creates a new session but doesn't attach to it. This is useful for system startup scripts.
I think it's something that could be called "daemon mode".
Maybe some environment variables must be set in order to execute screen and rtorrent? I've tried to set HOME manually but it didn't help.

How to start ASM instance at boot time - RHEL 2.1

Oracle 10.1.0.3
RHEL 2.1
I'm not able to get the ASM instance (not RAC) to start at boot time. It seems that the ocssd daemon does not finish starting until after all rc* scripts, including rc.local, have finished executing.
Patch 3458327 includes a new dbstart with header notes that are in conflict. The notes says that dbstart can't be used to start ASM until AFTER all rc* is finished. Then it continues and states that ASM instance startup should be put in rc.local.
As soon as I get logged on, a ps -ef|grep ocssd shows the daemon running. I can then manually start the ASM instance. There must be a way to get the ASM instance "auto" started at boot time.
Ideas?

The cheapest and administratively easiest way for me was to start Oracle instances (ASM and data) by "at" command :-) from rc scripts. Something like:
....echo "oracle start" | at now+2min....
Additionally the deferred startup has some additional advantages in my environment, so I am not motivated to look for better solution.
Best regards,
Pavel

How do I start slapd at boot time in leopard?

Greeting,
Forgive me if this is the wrong forum/community.
I want to start slapd at boot time on my new leopard upgrade. On tiger, it was as simple as having an LDAPSERVER=-YES- line in /etc/hostconfig. That does not seem to work for leopard. I can run slapd from the command line. I needed to make changes to the slapd.conf tiger version and reload my database, but all is working fine. I just have not been able to get the deamon to start at boot up. It must be simple. Any ideas?
Thanks,
--Linn

Texas Mac Man,
Thanks. Slapd is the OpenLDAP daemon (server) delivered with MacOS, even Client. No, starting at the user level is not what I need. I can already do that in a terminal window with /usr/libexec/slapd, after I get su'ed to root.
Think Unix, not iApps. When the system boots up, there should be scripts available to start specific daemons. I am looking for hints there.
BDAqua,
Thanks. I had seen that first discussion before. It deals with slapd failing when it tries to start on MacOS Server... where all these daemons indeed start at boot time. I am just trying to figure out how to do in leopard what I successfully did in tiger, namely start /usr/libexec/slapd at boot time.
And note, this is not an issue with slapd failing due to slapd.conf or database problems. All works fine from the user lever start.
Thanks,
--Linn

Auto starting Oracle at boot time

I have installed Oracle 11gr2 on Oracle Enterprise Linux successfully. Now i want to make oracle available automatically at boot time. I mean whenever server is up Oracle starts automatically.

It is not happening. I have to run dbstart script to make oracle available.
In ubuntu, we create /etc/init.d/oracledb script file, and with the use of following commands, oracle starts at boot time
chmod a+x /etc/init.d/oracledb
update-rc.d oracledb defaults 99
What i need is, its parallel for OEL.

Loading application at the boot time

Hi all!
Maybe somebody can answer my question:
How can I run my application at the boot time?
Thanks

We also have similar requirements. We are starting our script (which starts lot of processes) through inittab with options set to "once". We want this script to be executed only once in run level "3". But we noticed that the script is executed every time system moves into state "3".
Is there any way by which we can execute the process only during boot time and not otherwise?
Thank you for help
Dhananjay Joshi

Wired connection doesn't work if cable is not plugged in at boot time

Hey all,
I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
Here's some information regarding the system:
It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
The router is a Linksys EA2700/N600
journalctl -u NetworkManager
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
ping -c 10 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.38 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9014ms
rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 24 received, 76% packet loss, time 99062ms
rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
#noipv4ll
#Disable IPv6
#noipv6rs
#noipv6
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=keyfile
dhcp=dhcpcd
## Set static hostname
#[keyfile]
#hostname=foobar
## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.

Try to use dhclient perhaps? Might I also suggest letting systemd deal with the dhcp issue and not NM. That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card. I'm no guru but I got thinking about this when I saw this in your output:
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt.

[solved] wireless doesn't start at boot

I have BCM94311MCG wlan mini-PCI (rev 01) which works with b43 + wpa_supplicant nicely, except I can't seem to get to automagically start at boot time.
wlan0 always times out (wired connects at boot time just fine). I'd like my laptop to automatically connect to one of two networks, else remain disconnected.
Once started I can always netcfg2 <network name> and it connects no problem... I must have missed something in the wireless setup but I can't find what it is.
my rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="yes"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
MOD_AUTOLOAD="yes"
MOD_BLACKLIST=(!pcspkr !bcm43xx !ndiswrapper ) #deprecated
MOD_LOADLIST=(acpi-cpufreq cpufreq_ondemand slhc i8k tg3 fuse b43 ppdev snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
MODULES=( ${MOD_BLACKLIST[@]} ${MOD_LOADLIST[@]} )
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
HOSTNAME="myhostname"
# Interfaces to start at boot-up (in this order)
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(eth0 wlan0)
# Routes to start at boot-up (in this order)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
NETWORKS=("auto-wireless wlan0")
# DAEMONS
DAEMONS=(syslog-ng iptables @network @fusesmb @cups !netfs !crond @alsa @hal @dbus @fam @acpid @laptop-mode @cpufreq)
afaik the only unique thing I have in rc.conf is my fusesmb daemon (a script that mounts samba shares)
and my network.d/<network name>
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa-config"
ESSID="BCSI"
IP="dhcp"
TIMEOUT=20
when I look for wpa_supplicant after a boot, it is not running ( ps aux | grep wpa ).
wlan0 is up right after boot:
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:C5:08:1E:1C
inet addr:10.1.1.148 Bcast:10.1.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:fe08:1e1c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14443 errors:0 dropped:0 overruns:0 frame:0
TX packets:13281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8031647 (7.6 Mb) TX bytes:2248854 (2.1 Mb)
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1221 errors:0 dropped:0 overruns:0 frame:0
TX packets:1221 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:75880 (74.1 Kb) TX bytes:75880 (74.1 Kb)
wlan0 Link encap:Ethernet HWaddr 00:16:CE:67:85:B5
inet addr:169.254.55.57 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-16-CE-67-85-B5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
but since wpa_supplicant isn't running, it won't associate.
I'm misunderstading (I think) how netcfg2 is used during startup, I thought the line `NETWORKS=("auto-wireless wlan0")` would tell netcfg2 to try /etc/network.d/*
thanks for looking
Last edited by bioe007 (2008-04-30 14:19:12)

From: http://wiki.archlinux.org/index.php/Network_Profiles
"Ensure that net-profiles is in your rc.conf DAEMONS=() line."

Openntpd won't start at boot [SOLVED]

Hi all!
My system clock is perpetually off by 4 hours, and I've narrowed it down to an issue with Openntpd; it seems to be refusing to start at boot time. Here are the relevant lines from daemon.log:
Sep 1 21:30:26 raskolnikov ntpd[1440]: Terminating
and the output of ps aux | grep ntpd:
[raskolnikov@raskolnikov ~]$ ps aux | grep ntpd
ntp 1323 0.0 0.0 3184 700 ? S 17:32 0:00 /usr/sbin/ntpd -s
root 1332 0.0 0.0 3292 256 ? Ss 17:32 0:00 /usr/sbin/ntpd -s
1000 1412 0.0 0.0 3616 800 pts/0 S+ 17:33 0:00 grep ntp
I can manually restart the daemon via /etc/rc.d/openntpd restart, which works fine, and the time is set correctly. However, when I reboot, the adjustments are wiped out, and the daemon does not start again (same message in daemon.log). I have the default ntpd.conf. I have found very little helpful information on Google, I would greatly appreciate it if someone could point me in the right direction, I've wasted quite a few hours this evening working on this problem! Thanks!
Edit: Just in case it's helpful, here is my daemons array from rc.conf:
DAEMONS=(syslog-ng !network acpid eee hal networkmanager netfs crond openntpd bitlbee)
Last edited by happycodemonkey (2009-09-02 03:55:46)

I've had this problem too, although I do not use networkmanager. I've found that openntpd fails to configure itself properly if the network is not up when it starts (in my case this happens when I background the network daemon and start openntpd in the daemons array).
My current working solution* is to add this line to rc.local:
(sleep 300 && /etc/rc.d/openntpd start) &
That will wait 5 minutes before starting the openntpd daemon which gives the network more than sufficient time to start. An alternative would be run "/etc/rc.d/openntpd restart" in an hourly cronjob if your network settings change often.
* Why not just unbackground the network daemon you ask? If the network isn't up then it takes a while to timeout and I don't want to wait to boot in that case.
Last edited by Xyne (2009-09-02 02:05:52)

Process.Start(url) sometimes one instance fails

I need some help!!!
ASPX.NET/C#- Call Process.Start(url) several times, sometimes one instance fails without error!!
I have a program that calls a http aspx.net with arguments(URL) to execute some stuff. That program are invoking 10 times that aspx.net (all in the same time) with diferents urls.
But sometimes, one of the calls (url) do not launch in browser.
Code is very simple:
public partial class _Default : System.Web.UI.Page
private Object thisLock = new Object();
protected void Page_Load(object sender, EventArgs e)
try
string URL = Request.Params["URL"];
Logger.Log("CURRENT URL TO LAUNCH->", URL);
lock (thisLock)
ProcessStartInfo startInfo = new ProcessStartInfo("IExplore.exe");
startInfo.WindowStyle = ProcessWindowStyle.Maximized;
startInfo.Arguments = URL;
Process.Start(startInfo);
catch (Exception ex)
Logger.Log("Exception", ex);
}The URL launch are a client side technology!And that´s because i need to open the IE in WebServer!It´s silverlight web application to generate reports!The silverlight application closes the IE instances after finish. Everything goes right, except sometimes in 10 requests one fail
Thanks

What's the url do?
Is it possibly that the url isn't ready or there?
I can't recall ever doing process start from a web page.
Maybe there's an alternative way of approaching whatever you're trying to do.
BTW
I think you should probably ask this question in the asp.net forum since there's actually no Silverlight in the mix there
Hope that helps.
Recent Technet articles: Property List Editing;
Dynamic XAML

Strange error message when starting listener at boot time

Hi I have SuSE 10 server and Oracle 10.2.0
I followed the instruction on my how configure /etc/init.d/dbora to start
the db instance and the listener at boot time
The db instance starts fine;however, the listener doesnt start and gives the following strange message
"cannot start using /ade/vikrkuma_new/oracle/bin/tnslnr"
Does anyone has seen this and is there a workaround?
It looks like to me the listener tries to locate the listener.ora but it fails
I tried to force it by setting TNS_ADMIN in my /etc/init.d/dbora script but it still doesnt pick it up
any clue?

Hi,
Check your oracle bin varible and oracle home varible. If possible can you force this?
Cheers,
Kamalesh JK

How to get process start time from BI BPM Data Source

Hi,
I would like to get the process start time using the VC data source BI_BPM_MY_PROCESSES_DS.
The return parameter BI_START_TIME_VALUE returns numbers like 1.271.858.563.350,00. This seems to be ms beginning from 1970.
I tried the following to get the current date/time but it didn't work:
=DTADD(DATETIME(1970,01,01,00,00),@BI_START_TIME_VALUE,'Z')
Any idea how to do this?
Thanks,
Kevin

Hi Experts,
Do you have ideas for this SQL query ?
Regards.

[SOLVED] systemd/cron as user: timer doesn't start after boot

Hello,
I've tried to follow the wiki's systemd/cron functionality article to have a systemd service to run hourly.
Everything seems to be working ok, except that the hourly timer doesn't start automatically : I have to issue a
systemctl --user timer-hourly.timer start
command every time I start the machine to get the timer running.
Can you help me understand what I'm missing to get the (user) timer to start automatically after boot?
Thanks!
My setup consists of the following files:
/home/myuser/.config/systemd/user:
drwxr-xr-x 2 myuser users 4096 Jun 25 17:30 basic.target.wants/
-rw-r--r-- 1 myuser users 217 Jun 25 10:08 db_backup.service
-rw-r--r-- 1 myuser users 232 Jun 25 10:08 test.service
-rw-r--r-- 1 myuser users 61 Jun 19 12:14 timer-hourly.target
drwxr-xr-x 2 myuser users 4096 Jun 25 10:10 timer-hourly.target.wants/
-rw-r--r-- 1 myuser users 134 Jun 19 12:14 timer-hourly.timer
/home/myuser/.config/systemd/user/basic.target.wants/:
lrwxrwxrwx 1 myuser users 50 Jun 25 10:08 timer-hourly.timer -> /home/myuser/.config/systemd/user/timer-hourly.timer
/home/myuser/.config/systemd/user/timer-hourly.target.wants/:
lrwxrwxrwx 1 myuser users 49 Jun 13 15:51 db_backup.service -> /home/myuser/.config/systemd/user/db_backup.service
lrwxrwxrwx 1 myuser users 44 Jun 25 10:10 test.service -> /home/myuser/.config/systemd/user/test.service
timer-hourly.timer:
[Unit]
Description=Hourly Timer
[Timer]
OnBootSec=5min
OnCalendar=hourly
Unit=timer-hourly.target
[Install]
WantedBy=basic.target
timer-hourly.target:
[Unit]
Description=Hourly Timer Target
StopWhenUnneeded=yes
test.service:
[Unit]
Description=Run a test (echo) job every hour
Wants=timer-hourly.timer
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
ExecStart=/usr/bin/python /home/myuser/test_service.py
[Install]
WantedBy=timer-hourly.target
db_backup.service:
[Unit]
Description=Backups databases
Wants=timer-hourly.timer
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
ExecStart=/home/myuser/source/db_backups/db_backup.sh
[Install]
WantedBy=timer-hourly.target
test_service.py is a simple python script that appends the current time to a file, to check if the service is being run by the timer. (it is after I start the timer after boot, and runs correctly every hour)
db_backup.sh is a script that dumps a database into a text file in a mercurial repository, commits the change and pushes it to backup locations.
Last edited by fede (2014-06-25 21:06:09)

Have you tried this:
systemctl --user enable timer-hourly.timer

Process start at boot time..

Similar Messages

Maybe you are looking for