[Resolved]LXDM service vs Startx on boot

Quick Newbie Question:
I current have the lxdm service starting on boot. However I do not start startx on boot. Does this mean xorg and lxdm are not configured properly. Everything works fine as far as i can tell. Are there any consequences to not running lxdm through startx on boot. Input is appreciated :^) thanks!
Edit: I found this in my lxdm config file. Cons to running xserver with arg? "not fully function" meaning? thanks! :^)
[server]
## arg used to start xserver, not fully function
arg=/usr/bin/X -background vt1
# uncomment this if you really want xserver listen to tcp
# tcp_listen=1
# uncoment this if you want reset the xserver after logou
# reset=1
Last edited by armond (2015-02-03 01:33:16)

No real advantages, it's really just a matter of opinion.  Pick whichever way you prefer.

Similar Messages

  • New install hangs on boot when GDM or LXDM services are enabled

    Greetings Arch users,
    I've been trying out installing Arch on a USB drive in order to get familiar with the process and use it on my main machine in the future. I've been following the Beginners' Guide, and after a few hiccups, I managed to install what appears to be a fully-functional Arch system onto a 16 GB USB drive, albeit without a window manager or desktop environment.
    When I tried that is where I ran into problems. I installed X, vesa driver, and GNOME and enabled gdm.service, and upon the next reboot the system hung after or in the middle of the fsck process, exactly as described in this thread.
    rebooted, hangs after the fsck bit where it says something like /dev/sda4: clean, 112977/9296096 files, 185427/21217024 blocks
    I just get the blinking cursor. I left it there long enough to take a nap and nothing else came up.
    Examining the journalctl output, I see an error exactly like mentioned in this thread:
    GLib-GObject-CRITICAL: g_object_ref: assertion 'object->refcount > 0' failed
    GLib-GObject-CRITICAL: g_object_unref: assertion 'object->refcount > 0' failed
    Chrooting into the system and disabling gdm.service allowed for normal boot.
    Well, I thought, maybe there's an issue with GDM or GNOME. I'll try LXDE and LXDM instead. Unfortunately, that hung at the exact same point in the loading process. Looking at the journalctl, I saw an output exactly like what was described in this thread:
    Lxdm.service main process exited code=exited status=1/FAILURE
    lxdm.service entered failed state
    I'm stumped. I've searched and haven't come up with anything. Does anyone have any ideas about what might be the cause? What additional information would be helpful in diagnosing the issue? Thank you for your help.
    Last edited by AbortToddlers (2014-01-28 15:06:04)

    Neburski wrote:
    slowpoke1584 wrote:
    killall gdm
    GDM then restarts immediately. Problem recurring each boot.
    Can you check the logs (dmesg, journalctl, xorg) and see if there are any differences for the startup of GDM before and after a successful GDM start.
    Technically from the lack of information you provided it's not possible to state if you actually have the same issue or not. It might be better for you to start your own separate thread.
    If you start your separate thread please provide some more details so people don't need to start guessing.
    I think I'll just RTM.

  • [SOLVED!] Archiso -- KDM - LXDM don't start at boot (enabled)

    Hello,
    I have installed on this computer my customized Archiso (with no special configurations). I have enabled kdm.service, but nothing happened. After reboot either.
    I have now tried with LXDM, same thing. With "systemctl status" I usually get something like: "enabled, dead"
    If I start kdm or lxdm manually, it works.
    sudo systemctl start lxdm; sudo systemctl status lxdm
    lxdm.service - LXDE Display Manager
    Loaded: loaded (/usr/lib/systemd/system/lxdm.service; enabled)
    Active: active (running) since vie 2013-03-29 13:54:08 UTC; 46min ago
    Main PID: 319 (lxdm-binary)
    CGroup: name=systemd:/system/lxdm.service
    └─321 /usr/bin/X :0 vt07 -nolisten tcp
    ‣ 319 /usr/sbin/lxdm-binary
    mar 29 13:54:08 ubunchu systemd[1]: Starting LXDE Display Manager...
    mar 29 13:54:08 ubunchu systemd[1]: Started LXDE Display Manager.
    mar 29 13:54:12 ubunchu lxdm-binary[319]: pam_unix(lxdm:session): session opened for user ubunchu by (uid=0)
    Dmesg: http://pastie.org/private/8n97afoezf3urejz3qizeq
    On some posts they mentioned that maybe nvidia or a module starts up too late, or the login managers too early.
    Any tips/hints on what should I try?
    Thanks in advance.
    Cheers!
    Last edited by ubunchu (2013-04-22 22:06:12)

    At boot I can get:
    [root@ubunchu ~]# systemctl status kdm
    kdm.service - K Display Manager
    Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled)
    Active: inactive (dead)
    [root@ubunchu ~]# ls -al /etc/systemd/system/
    total 32
    drwxr-xr-x 4 root root 4096 abr 10 22:51 .
    drwxr-xr-x 5 root root 4096 abr 18 09:10 ..
    -rw-r--r-- 1 root root 1660 mar 23 16:43 [email protected]
    lrwxrwxrwx 1 root root 46 mar 24 13:39 dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
    lrwxrwxrwx 1 root root 41 mar 23 15:50 default.target -> /usr/lib/systemd/system/multi-user.target
    -rw-r--r-- 1 root root 230 mar 7 14:07 dhcpcd.service
    lrwxrwxrwx 1 root root 35 abr 10 22:51 display-manager.service -> /usr/lib/systemd/system/kdm.service
    -rw-r--r-- 1 root root 134 mar 7 14:07 etc-pacman.d-gnupg.mount
    drwxr-xr-x 2 root root 4096 abr 18 09:10 multi-user.target.wants
    drwxr-xr-x 2 root root 4096 mar 24 13:39 network.target.wants
    -rw-r--r-- 1 root root 325 mar 7 14:07 pacman-init.service
    On every system I install my custom archiso (basic install) the same thing happens, what am I missing?

  • Resolve database service name using in SQL

    Hi all!
    My question is:
    Is it possible to resolve database service name (e.g. TNS) from SQL only (without logging into the server with oracle user and execute tnsping)?
    I'll give you a bit background about my question:
    In DataGuard, if you query v$archive_dest, you can see the SERVICE NAME of the standby database in the STANDBY records. I would like to know what is the real server name and database instance of the standby database.
    I don't want to login to the primary server with oracle user (let's say that I can not - it's a program really, not me...).
    Let's also say that the only user I have is a read-only user to the database (with grants to all tables and views, but cannot execute privileged DBMS sys packages).
    Running "SQL> host tnsping NAME" doesn't do the job, since this is only for SQL plus.
    Doe's anyone have any idea? maybe v$ view that contains the TNS resolution (tried to find, no success)? maybe a tnsping alike command/function?
    Thanks a lot!
    Maayan

    MaayanB wrote:
    I'll explain the reason.
    I'm working on an agentless product that connects to databases, storage and hosts, and models them into a small CMDB.
    Since my product needs to model the "STANDBY" relationship between primary and standby DataGuard databases - I need to be able to resolve the value of the "DESTINATION" field from "V$ARCHIVE_DEST", where TARGET IN ('STANDBY','REMOTE').
    I could login to the server and execute "tnsping DBNAME", but the problem is that when a server has more than one ORACLE_HOME (hence, more than one tnsname.ora file), I need to make sure that the user I'm using to login to the server has all environment variables conigured properly for each database installed on the server (BTW, the unix user is also a "naked" user with no privileges except the sudo's defined for it).
    So I assume that the best way to be sure that the environment variables are correctly defined is when I login to the database.
    This is the reason I need to resolve service names using SQL.
    BTW, the database process somehow uses the Oracle Net Services to resolve the same value when it sends the redo log files to the standby server - and I'd like to resolve it the same way (or other, if not possible). If it uses the sys privileges, and it executes the package that lets you execute something on the server ("tnsping", in this case), and this is the only way it can be done - I need to start thinking on a different way to resolve the problem.What you are missing is that when "the database process somehow uses the Oracle Net Services to resolve the same value when it sends the redo . . ." is that Net services is NOT just resolving the name for the database. It is also handling the actual transport of the files. That name resolution is not passed back to the database.
    >
    Anyway, I'm not a hacker or something alike, It's just that my product doesn't know how to pick up the phone and dial :)

  • Unable to resolve 'tuxedo.services.TuxedoConnection'

    Hi
    I've just installed BEA Weblogic 7.0. I am currently using the examples server.
    I have attempted to set up the WTC, but I am getting the following error:
    Beginning statefulSession.Client...
    Creating Toupper
    converting allcaps
    *** here ***
    tperrno encountered: TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not get
    Tu
    xedoConnectionFactory : javax.naming.NameNotFoundException: Unable to resolve
    't
    uxedo.services.TuxedoConnection' Resolved: 'tuxedo.services' Unresolved:'TuxedoC
    onnection' ; remaining name 'TuxedoConnection'
    Start server side stack trace:
    TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not get TuxedoConnectionFactory
    : javax.naming.NameNotFoundException: Unable to resolve 'tuxedo.services.Tuxedo
    Connection' Resolved: 'tuxedo.services' Unresolved:'TuxedoConnection' ; remainin
    g name 'TuxedoConnection'
    at examples.wtc.atmi.simpapp.ToupperBean.Toupper(ToupperBean.java:116)
    at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl.Toupper(ToupperBe
    an_8roqg7_EOImpl.java:46)
    at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
    bleServerRef.java:87)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:762)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    End server side stack trace
    End statefulSession.Client...
    Does anyone have any information?
    Many thanks.
    Rennay

    Hi
    The problem was that I didnt specify the "//" for the network address.
    Thanks.
    "Rennay" <[email protected]> wrote:
    >
    Hi
    I've just installed BEA Weblogic 7.0. I am currently using the examples
    server.
    I have attempted to set up the WTC, but I am getting the following error:
    Beginning statefulSession.Client...
    Creating Toupper
    converting allcaps
    *** here ***
    tperrno encountered: TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could
    not get
    Tu
    xedoConnectionFactory : javax.naming.NameNotFoundException: Unable to
    resolve
    't
    uxedo.services.TuxedoConnection' Resolved: 'tuxedo.services' Unresolved:'TuxedoC
    onnection' ; remaining name 'TuxedoConnection'
    Start server side stack trace:
    TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not get TuxedoConnectionFactory
    : javax.naming.NameNotFoundException: Unable to resolve 'tuxedo.services.Tuxedo
    Connection' Resolved: 'tuxedo.services' Unresolved:'TuxedoConnection'
    ; remainin
    g name 'TuxedoConnection'
    at examples.wtc.atmi.simpapp.ToupperBean.Toupper(ToupperBean.java:116)
    at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl.Toupper(ToupperBe
    an_8roqg7_EOImpl.java:46)
    at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
    bleServerRef.java:87)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:762)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    End server side stack trace
    End statefulSession.Client...
    Does anyone have any information?
    Many thanks.
    Rennay

  • ORA-12154 TNS Could not resolve the service name

    I am working on Oracle 9i(Release 2) windows version. I want to change the value of
    shared pool size, buffer size and others database parameter through "Enterprise Manager Console" but
    when i connect to sysdba mode message comes "ORA-12154 TNS Could not resolve the service name".
    How can I solve this problem?

    these problem are you getting from OEM?
    post
    lsnrctl status
    lsnrctl services
    make sure database is running.. all the services running in services.msc
    check error code and start..
    ORA-12514:
         TNS:listener does not currently know of service requested in connect descriptor
    Cause:      The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
    Action:      
    - Wait a moment and try to connect a second time.
    - Check which services are currently known by the listener by executing: lsnrctl services <listener name>
    - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
    - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
    - Check for an event in the listener.log file.

  • [solved] Large number of services enabled during first boot

    I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
    To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
    Any ideas as to what might be causing this?
    Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
    Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
    Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
    Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
    Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
    getty.target.wants:
    * [email protected]
    multi-user.target.wants:
    * [email protected]
    * iptables.service
    * remote-fs.target
    * sshd.service
    sysinit.target.wants:
    (none)
    Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
    default.target.wants:
    * systemd-readahead-collect.service
    * systemd-readahead-replay.service
    multi-user.target.wants:
    * dhcpcd.service * krb5-kpropd.service
    * fstrim.service * nscd.service
    * ftpd.service * rsyncd.service
    * gpm.service * systemd-journal-upload.service
    * ip6tables.service * systemd-networkd.service
    * krb5-kadmind.service * systemd-resolved.service
    * krb5-kdc.service
    sockets.target.wants:
    * krb5-kpropd.socket * systemd-journal-remote.socket
    * rlogin.socket * talk.socket
    * rsh.socket * telnet.socket
    * rsyncd.socket * uuidd.socket
    * sshd.socket
    sysinit.target.wants:
    * dm-event.service
    * systemd-timesyncd.service
    system-update.target.wants:
    * systemd-readahead-drop.service
    Explicitly installed packages:
    dhcpcd iputils procps-ng systemd-sysvcompat
    diffutils linux-grsec psmisc tar
    dnsutils logrotate reflector vim-systemd
    file mlocate rsync wget
    gradm mtr s-nail which
    grub openssh screen whois
    inetutils pacman
    Last edited by tazmanian (2014-09-10 23:11:42)

    +1.
    Here is the ports these services are listening:
    $ ss -tpl
    State      Recv-Q Send-Q                                                                                                       Local Address:Port                                                                                                           Peer Address:Port   
    LISTEN     0      128                                                                                                                      *:llmnr                                                                                                                     *:*       
    LISTEN     0      128                                                                                                                      *:ssh                                                                                                                       *:*       
    LISTEN     0      128                                                                                                                     :::llmnr                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::19532                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::tell                                                                                                                     :::*       
    LISTEN     0      128                                                                                                                     :::ssh                                                                                                                      :::*       
    LISTEN     0      128                                                                                                                     :::telnet                                                                                                                   :::*       
    LISTEN     0      128                                                                                                                     :::login                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::shell                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::rsync                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::git                                                                                                                      :::*

  • Trying to create a service that starts at boot

    People,
    I'm trying to create a service that will start at boot (in single-user mode, actually). I am up and running but I do NOT want to run the service now. I only want to run the service when the machine reboots.
    I've been rummaging around all day trying to figure this out but I'm stuck. I can create a service that runs. I can create an XML file in /var/svc/manifest/site/patch-install.xml that will be read when I boot- because after I boot, I can list the service:
    svcs -a | grep patch
    disabled       18:23:23 svc:/site/patch-install:defaultI have inserted the following in my xml:
    <create_default_instance enabled='true' />and also
    <create_default_instance enabled='false' />but it makes no difference. Anyone have any idea? What is the purpose of create_default_instance? I don't understand; item 9 on http://www.sun.com/bigadmin/content/selfheal/sdev_intro.html seems rather opaque to me.
    Also, what exactly is the purpose of /var/svc/profile/ ? I tried putting some code to enable my xml but it didn't do anything. Just wondering if this might fit into the picture.
    BTW, I do not want the login prompt to appear until my method is complete.
    Thanks.
    -mschwage
    Here fyi is my /var/svc/manifest/site/patch-install.xml file:
    <?xml version="1.0"?>
    <!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
    <service_bundle type='manifest' name='Patches:patch-install'>
    <service
            name='site/patch-install'
            type='service'
            version='1'>
            <create_default_instance enabled='false' />
            <single_instance />
            <dependent
                    name='patch-install_single-user'
                    grouping='require_all'
                    restart_on='none'>
                    <service_fmri value='svc:/milestone/single-user' />
            </dependent>
            <exec_method
                    type='method'
                    name='start'
                    exec='/var/tmp/S92delay'
                    timeout_seconds='86400' />
            <exec_method
                    type='method'
                    name='stop'
                    exec=':true'
                    timeout_seconds='0' />
            <property_group name='startd' type='framework'>
                    <propval name='duration' type='astring' value='transient' />
            </property_group>
            <stability value='External' />
            <template>
                    <common_name>
                            <loctext xml:lang='C'>
                            Install patchset upon boot.
                            </loctext>
                    </common_name>
            </template>
    </service>
    </service_bundle>

    Hushpuppy wrote:
    People,
    I'm trying to create a service that will start at boot (in single-user mode, actually). I am up and running but I do NOT want to run the service now. I only want to run the service when the machine reboots.I'd probably create the service now (by importing the manifest manually rather than waiting for the reboot), then set general/enabled in the default instance to be be true with svcprop. That should tell it to start at boot, but not enable it immediately.
    I've been rummaging around all day trying to figure this out but I'm stuck. I can create a service that runs. I can create an XML file in /var/svc/manifest/site/patch-install.xml that will be read when I boot- because after I boot, I can list the service:Yes, that's the default. Or you can load it immediately to create the service now.
    # svccfg import patch-install.xml
    I have inserted the following in my xml:
    <create_default_instance enabled='true' />and also
    <create_default_instance enabled='false' />but it makes no difference. Anyone have any idea? What is the purpose of create_default_instance? I don't understand; item 9 on http://www.sun.com/bigadmin/content/selfheal/sdev_intro.html seems rather opaque to me.There's a difference between a "service" like network/smtp or console-login and an "instance" like network/smtp:sendmail or console-login:default. In most cases, you just want a single "default" instance of your service. The above line sets the default instance 'enabled' property to true or false. When I import your manifest as is, the service comes in as 'disabled'. If I set it to true, it comes in as 'maintenance' (almost certainly because it was enabled, tried to start, and couldn't find the start method on my machine).
    Also, what exactly is the purpose of /var/svc/profile/ ? I tried putting some code to enable my xml but it didn't do anything. Just wondering if this might fit into the picture.'profiles' are loaded exactly once, and they are mainly used to set certain services to enabled or disabled.
    3 of them are loaded if present, platform.xml, generic.xml, and site.xml. The last is not generated by the OS, but left for you to use. But it's usually only useful as a "first boot" type thing. Because if you make changes to it, it will not be reread. This isn't usually a problem because after first boot you're in control of the services. The usual thing is that at first boot the manifests load to create services, then the profiles are loaded to set then enabled or disabled. This isn't possible before that point because there's no service to modify yet.
    BTW, I do not want the login prompt to appear until my method is complete.Any login prompt like a network login, or only the console login prompt? If the latter, then you'll want a dependency so that system-console-login depends on your service. But if your service has a problem at boot time, you'd make it difficult to log in.
    Darren

  • Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

    Hi
    I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
    Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
    The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
    I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
    I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
    I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
    Cheers   

    Hi Joel,
    This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
    The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
    should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
    The related KB:
    PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
    http://support.microsoft.com/kb/259670
    The similar thread:
    PXE-E53: No boot filename received
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
    WDSServer (Windows Deployment Server) Fails to Start
    http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
    I’m glad to be of help to you!
    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.

  • Network Store Interface Service - Memory Leak on Boot

    I wanted to compile and explain my solution to an issue in Windows 8.1 where NSI causes major RAM/Disk utilization in creating four files in C:\Windows\System32\networklist\icons
    Related Threads
    http://social.technet.microsoft.com/Forums/en-US/bebbd935-f6f8-47fb-b756-714c27f0da7d/win-81-rtm-slow-startup-thanks-to-network-list-service?forum=w81previtpro
    http://social.technet.microsoft.com/Forums/windows/en-US/35aa5d51-89d4-4dfa-a4fa-1138ff8b43c8/system-slowfreezes-on-startup-svchostexe-uses-8gb-ram

    Prior to noticing sluggish behavior during startup, I decided I wanted to give my Network a personalized name "Grimm Network." I achieved that by following this process: http://www.eightforums.com/tutorials/19670-network-name-change-windows-8-a.html
    The error of my ways started when I poked around further...I changed Network Icon -> Icon to "Icon" from "Not Configured"
    That is what trigger this startup behavior.
    I went back and changed the setting to "Not Configured"
    The registry entries referenced in the related posts I shared above were removed. Sure enough the files were no longer being deleted/created at boot.
    This explanation is much more palatable than deleted registry entries with no further explanation was is advised in the other threads.
    Prior to finding the other two threads, I did have to do some trial and error with root causing the services. With Task manager, I narrowed it down to 7 services. Then with Safe Mode w/ Networking, I narrowed it now to NSI and NETPROFM. After disabling NSI
    during a normal boot, I noticed the issue was not happening. I then realized that there was a large amount of disk utilization, that allowed me to use Resource Monitor to see what files were being affected. Then searching for NSI related issue with Windows
    8.1 led me to the above When reading through the related posts, it finally hit me when I saw that the registry entries were related to my custom named network...I remembered that I had changed some settings, specifically with the icon in SECPOL.MSC, and that
    it must be related. This is how I deduced a non-registry entry changing solution to this problem.
    In summary, go to SECPOL.MSC -> Network List Manager Policies ...
    Look for your networks, open them up, and ensure that Network Icon -> Icon has "Not Configured" selected. 
    I hope this helps other people.
    -Gary

  • Service Template and iSCSI Boot Parameters

    Hello,
    I use updating service templates to ensure all service profiles are the same and it works great. We have recently setup a Nimble storage array and for iSCSI boot you have to put the target of of the boot LUN in the iSCSI boot parameters. However as each profile will have to boot from a different volume. This causes an issue as I cant change a service profile that is bound to a service template and i need the profiles to have differnt boot volumes.
    Am I missing something here.
    Thanks

    The service profile requires two different IQNs one for the initiator/server and one for the target/storage_array. What I’m saying is that each initiator needs to have a different IQN but all of them can use the same target IQN to communicate to the storage.
    If you are using an updating template to update all of the service profiles, any change you make there will be propagated to all of the service profiles that were created from this template, which means that you can only make changes to the template and not directly to the service profiles unless you unbind them from this template. 
    The main thing you need to understand is that if you use the same target IQN it doesn’t mean that all of your server are going to try to boot to the same LUN as long as you group their IQN (initiator) to a dedicated LUN on the storage array.
    Let me kwow what you think
    iSCSI
    http://en.wikipedia.org/wiki/ISCSI

  • [solved] systemd services not starting at boot (or at all)

    On my router, some systemd services fail to start at boot.
    The services are :
    adsl (pppoe connetction on the wan interface)
    shorewall (funny again for a router)
    logind (brings up only tty1, and not the others with a 'timeout' error)
    adsl starts fine manually after booting up
    the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
    I really don't know, what happened to logind...
    Last edited by scar (2012-11-30 10:20:44)

    cups: avahi client failed
    adsl: timeout (ppp0 running on eth0, the service did not found eth0)
    shorewall: did not work by the systemctl command, only with the old rc script
    I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
    since this was a very old install (but up to date), I've decided to reinstall the whole thing,
    Everything works
    (But reinstalling does not solve any problem, it erases the problems...)
    Last edited by scar (2012-11-30 10:21:20)

  • MSI Install - Service Startup Causing a Boot Loop?

    Windows 7
    I created a service executable in C++ and made an MSI with InstallShield 2014. I added the needed runtimes for the service and go through the MSI install process. Service starts fine, works great, everything is behaving as expected.
    I initiate a reboot to ensure the service behaves as normal.
    After the reboot a dialog pops up (Presumed from MSI?) that a reboot is required again. Strange it didn't ask before the reboot, but clicking yes to this dialog shuts down the system.
    On THIS boot up the system goes through the windows start up and is about to login to the user with the login screen appearing, but then suddenly the system reboots, and it will continuously do this.
    Loading last known good configuration allows you to login again, but the same "Reboot REquired" dialog appears, and clicking yes restarts the boot loop failure.
    How can I tell what is happening that is requiring the reboot? How can I debug what is causing windows to suddenly shutdown and reboot?
    If I install everything and never tell the MSI to start the service, everything is fine.
    As for the service itself, it literally just connects up to SCM and does little else. It's basically a framework to actually fill in the functionality.
    Hoody Hoo!

    Hello RevenantCoder,
    For issues regarding  InstallShield 2014, it is beyond the scope of our support, you could post it to:
    https://community.flexerasoftware.com/forumdisplay.php?133-InstallShield
    Thanks for your understading.
    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.
    Click
    HERE to participate the survey.

  • Is there any way to query who resolved a Service Request in Service Manager?

    Hi,
    I have a query that pulls the last name of the user who resolved an Incident in Service Manager. The name is pulled from a view called "IncidentResolvedByUserFactvw." I need to pull the last name of the person who completed a Service Request. There
    is no view or table that I can find that has this info. Is there a "IncidentResolvedByUserFactvw" type view with the Service Request info? If not where is this data stored?
    Thank you for any help!

    couple of notes:
    necromancy!
    Closed -ne Completed. Completed means the work has been delivered. Closed means the work has been delivered, the client has been contacted, we've finished all of our followups and process checks, and we're ready to archive this ticket in the historical
    database. 
    it doesn't really make sense to talk about who completed a service request. a service request is a structured process. as well as who built an item that came off the assembly line; the assembly line did. who completed the services request? if your service
    requests are well designed, the overwhelming majority of requests will be completed by the system once the last activity in the process is completed. 

  • Edit services which start at boot

    I need to add some services to my boot sequence which are launched by the launchd...
    yes... to fix the bug that Apple's latest update has caused with pboard and Spotlight not starting.
    I can manually start these services from a terminal window using launchctl but what I'd really like to know is where are the scripts that govern what services are loaded as OSX starts, because obviously that's where the problem is.

    I see, so it just cycles through them at the boot sequence looking at when theyre meant to be launched...
    Hmmm, Justin your posts have been very helpful in learning how OSX launches boot services but I'm now totally stuck as to why pboard (most important), Spotlight and UserEventAgent will not load even though their plists are exactly the same as on my other mac that works... I've even checked the binaries that these things relate to and the files seem fine.
    Totally stuck now. I can't bear the thought of a clean install for a seemingly simple problem.
    Is there any way OSX can repair its system files from install CD without a major reinstall?

Maybe you are looking for