Systemd and cifs unmount at shutdown problem

I have configured my cifs mounts in /etc/fstab, they have the noauto,x-systemd.automount option. (not the cause of the problem, but theoretically systemd should handle it better)
It all works ok, except at shutdown. Systemd brings the network down BEFORE unmounting the cifs mounts. This results in 1m30s of wait until the unmount fails due to timeout.
This has been happening a long time ago. When I'm in a hurry I just use sysrq to terminate all, but I would like to disable the sysrq key in my system.
Any clues?
* It happens with wicd and networkmanager
Last edited by eduardo.eae (2014-03-04 22:46:25)

seiichiro0185 wrote:
I had this problem too in the beginning, but did solve it by setting the hostid like this:
~# hostid > /etc/hostid
After this I rebuilt my initrd with
~# mkinitcpio -p linux
After these two steps I could remove the zfs_force from my kernel line and it works without a problem since then.
This solution f*******ed up my installation and now i'am have a real pain to reinstall my system because there is a version problem with the zfs module :
https://bbs.archlinux.org/viewtopic.php … 0#p1331360
And it may also have f***ed up my dd.
Bussiere

Similar Messages

Less than 24hrs and already getting the shutdown problem

I recieved my macbook (black 1GB Ram) yesterday evening, after spending a few hours loading up my software and running updates for everything i was happy and running great. Since it was midnight i decided to get some sleep and enjoy my beauty in the morning. At night with the coreDuo temp checker and iStat Nano i was running at Max 56C, mostly 26C. This morning i came out and opened the lid (left it on with just the lid closed) and she came right out of sleep no problem. used it for about 3mins and it just shut off...took about 5 times of hitting the power button for it to come back on (i waited a few mins between tries). When i left for work i had it back up and running, instead of leaving it on i'm going to try and turn it off when i'm done using it. It's a pain in the butt but i want to see if that helps or has no effect on the problem. Any suggestions? I know the holding the power button until it beeps is supposed to help, but this is BRAND NEW and i expect quality from Apple, that is why i buy it, so i expect it to work as it was designed.

Is it running 10.4.7 ? Mine came with 10.4.6 installed and only started shutting down after I upgraded to 10.4.7
I've also noticed a strange phenomomen I can't explain. Mine started shutting down only when it was running from the battery. I followed the tips from various forums suggesting that resetting a PMU reset might help (if only temporarily) which I did and certainly cleared the problem. However, this activated the other issue/bug of booting up with a blank white screen with multiple vertical lines. I cleared this problem by performing PRAM reset and immediately changing the screen resolution to another resolution and then changing it back again. Everything worked fine then UNTIL:
I completely drained the battery and charged it up again over night. I switched on and it shutdown immediately with the battery on 100%. No amount of performing a PMU reset or PRAM would make the Macbook work again on the battery.
I guessed that if the Macbook wouldn't work with a 100% charged battery then maybe it would work with a less than 100% battery. But I couldn't work out how to drain the battery if it kept shutting down. So, I put the Macbook to sleep with the power adaptor running it, and then when it was asleep I took the power lead out so that it slept using the battery. To my surprise it didn't shutdown! I left it in sleep mode running on battery for about 30 minutes and now it's working again on the battery!
Does anyone suspect, like me that this is a software problem with OS X and not a hardware problem?
Sorry if this is very prolix, but the more we learn about this problem the closer Apple and us might get to finding out exactly what's happening here.
iMac G4 15" flat screen : MacBook 1.83 (Tiger) Mac OS X (10.3.9)

Slow shutdown/reboot due to failing cifs unmount

I have a few cifs (samba) shares in my fstab like so:
#NAS
//xxx.xxx.xxx.xxx/video /media/nas/video cifs credentials=/home/f3bruary/.samba_creds 0 0
//xxx.xxx.xxx.xxx/downloads /media/nas/downloads cifs credentials=/home/f3bruary/.samba_creds 0 0
//xxx.xxx.xxx.xxx/music /media/nas/music cifs credentials=/home/f3bruary/.samba_creds 0 0
//xxx.xxx.xxx.xxx/public /media/nas/public cifs credentials=/home/f3bruary/.samba_creds 0 0
//xxx.xxx.xxx.xxx/logs /media/nas/logs cifs credentials=/home/f3bruary/.samba_creds 0 0
And my reboots and shutdowns are a bit slow and I notice the mounts aren't being unmounted properly. They timout which takes about 2 minutes and then the reboot/shutdown continues.
...snip...
Jun 11 20:31:26 ultracool systemd[1]: Stopped TLP system startup/shutdown.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Bluetooth service...
Jun 11 20:31:26 ultracool systemd[1]: Stopped target Multi-User System.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Multi-User System.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Daily locate database update.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Daily locate database update.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Periodic Command Scheduler...
Jun 11 20:31:26 ultracool systemd[1]: Stopped Weekly pkgstats submission.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Weekly pkgstats submission.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Jun 11 20:31:26 ultracool systemd[1]: Stopping D-Bus System Message Bus...
Jun 11 20:31:26 ultracool systemd[1]: Stopped Daily verification of password and group files.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Daily verification of password and group files.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Login Service...
Jun 11 20:31:26 ultracool systemd[1]: Stopped Daily man-db cache update.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Daily man-db cache update.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Permit User Sessions...
Jun 11 20:31:26 ultracool systemd[1]: Stopped target Login Prompts.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Login Prompts.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Daily rotation of log files.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Daily rotation of log files.
Jun 11 20:31:26 ultracool bluetoothd[717]: Terminating
Jun 11 20:31:26 ultracool avahi-daemon[716]: Got SIGTERM, quitting.
Jun 11 20:31:26 ultracool bluetoothd[717]: Stopping SDP server
Jun 11 20:31:26 ultracool bluetoothd[717]: Exit
Jun 11 20:31:26 ultracool crond[712]: (CRON) INFO (Shutting down)
Jun 11 20:31:26 ultracool connmand[729]: D-Bus disconnect
Jun 11 20:31:26 ultracool avahi-daemon[716]: avahi-daemon 0.6.31 exiting.
Jun 11 20:31:26 ultracool connmand[729]: Remove interface eno1 [ ethernet ]
Jun 11 20:31:26 ultracool connmand[729]: Remove interface wlo1 [ wifi ]
Jun 11 20:31:26 ultracool systemd[1]: Stopping Initialize hardware monitoring sensors...
Jun 11 20:31:26 ultracool systemd[1]: Stopping Samba NetBIOS name server...
Jun 11 20:31:26 ultracool nmbd[799]: [2015/06/11 20:31:26.471220, 0] ../source3/nmbd/nmbd.c:58(terminate)
Jun 11 20:31:26 ultracool nmbd[799]: Got SIGTERM: going down...
Jun 11 20:31:26 ultracool nmbd[799]: [2015/06/11 20:31:26.474074, 0] ../source3/libsmb/nmblib.c:873(send_udp)
Jun 11 20:31:26 ultracool nmbd[799]: Packet send failed to 192.168.1.255(138) ERRNO=Invalid argument
Jun 11 20:31:26 ultracool nmbd[799]: [2015/06/11 20:31:26.474862, 0] ../source3/libsmb/nmblib.c:873(send_udp)
Jun 11 20:31:26 ultracool nmbd[799]: Packet send failed to 192.168.1.255(138) ERRNO=Invalid argument
Jun 11 20:31:26 ultracool systemd[1]: Stopped Periodic Command Scheduler.
Jun 11 20:31:26 ultracool systemd[1]: Stopped D-Bus System Message Bus.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Bluetooth service.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Permit User Sessions.
Jun 11 20:31:26 ultracool systemd[1]: Stopped target Remote File Systems.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Remote File Systems.
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/music...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/video...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/downloads...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/public...
Jun 11 20:31:26 ultracool systemd[1]: Stopped target Remote File Systems.
Jun 11 20:31:26 ultracool systemd[1]: Stopping Remote File Systems.
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/music...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/video...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/downloads...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/public...
Jun 11 20:31:26 ultracool systemd[1]: Unmounting /media/nas/logs...
Jun 11 20:31:26 ultracool systemd[1]: Stopped Initialize hardware monitoring sensors.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Login Service.
Jun 11 20:31:26 ultracool systemd[1]: Stopped target User and Group Name Lookups.
Jun 11 20:31:26 ultracool systemd[1]: Stopping User and Group Name Lookups.
Jun 11 20:31:26 ultracool kernel: [UFW AUDIT] IN= OUT=wlo1 SRC=0.0.0.0 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 MARK=0xe4
Jun 11 20:31:26 ultracool kernel: [UFW ALLOW] IN= OUT=wlo1 SRC=0.0.0.0 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 MARK=0xe4
Jun 11 20:31:26 ultracool connmand[729]: eno1 {remove} index 2
Jun 11 20:31:26 ultracool connmand[729]: wlo1 {remove} index 3
Jun 11 20:31:26 ultracool connmand[729]: Exit
Jun 11 20:31:26 ultracool systemd[1]: Stopped Connection service.
Jun 11 20:31:26 ultracool systemd[1]: Stopped Samba NetBIOS name server.
Jun 11 20:32:56 ultracool systemd[1]: media-nas-logs.mount unmounting timed out. Stopping.
Jun 11 20:32:56 ultracool systemd[1]: media-nas-downloads.mount unmounting timed out. Stopping.
Jun 11 20:32:56 ultracool systemd[1]: media-nas-video.mount unmounting timed out. Stopping.
Jun 11 20:32:56 ultracool systemd[1]: media-nas-music.mount unmounting timed out. Stopping.
Jun 11 20:32:56 ultracool systemd[1]: media-nas-public.mount unmounting timed out. Stopping.
Jun 11 20:33:16 ultracool systemd[1]: Unmounted /media/nas/video.
Jun 11 20:33:16 ultracool systemd[1]: Unit media-nas-video.mount entered failed state.
Jun 11 20:33:16 ultracool systemd[1]: Unmounted /media/nas/logs.
Jun 11 20:33:16 ultracool systemd[1]: Unit media-nas-logs.mount entered failed state.
Jun 11 20:33:16 ultracool systemd[1]: Unmounted /media/nas/music.
Jun 11 20:33:16 ultracool systemd[1]: Unit media-nas-music.mount entered failed state.
Jun 11 20:33:16 ultracool systemd[1]: Unmounted /media/nas/public.
Jun 11 20:33:16 ultracool systemd[1]: Unit media-nas-public.mount entered failed state.
Jun 11 20:33:42 ultracool systemd[1]: Unmounted /media/nas/downloads.
Jun 11 20:33:42 ultracool systemd[1]: Unit media-nas-downloads.mount entered failed state.
Jun 11 20:33:42 ultracool systemd[1]: Stopped target Remote File Systems (Pre).
Jun 11 20:33:42 ultracool systemd[1]: Stopping Remote File Systems (Pre).
Jun 11 20:33:42 ultracool systemd[1]: Stopped target NFS client services.
Jun 11 20:33:42 ultracool systemd[1]: Stopping NFS client services.
Jun 11 20:33:42 ultracool systemd[1]: Stopping GSSAPI Proxy Daemon...
Jun 11 20:33:42 ultracool systemd[1]: Stopped target Network is Online.
Jun 11 20:33:42 ultracool systemd[1]: Stopping Network is Online.
Jun 11 20:33:42 ultracool systemd[1]: Stopped target Network.
Jun 11 20:33:42 ultracool systemd[1]: Stopping Network.
Jun 11 20:33:42 ultracool systemd[1]: Stopping Network connectivity (wlo1)...
Jun 11 20:33:42 ultracool systemd[1]: Stopped GSSAPI Proxy Daemon.
Jun 11 20:33:42 ultracool systemd[1]: Stopped Network connectivity (wlo1).
Jun 11 20:33:42 ultracool systemd[1]: Removed slice system-network.slice.
...snip...

If anyone could give me a kick in the right direction to fix this, I'd appreciate it.

[SOLVED]Problem with systemd and awesome wm

Hello,
I recently have installed systemd and I have enabled slim.service, but after logging in throught slim I cannot run any programs in my awesome wm. Well, actually I can, but only a few seconds after login. If I run xterm and then try to run a program throught it I get messages "no protocol specified" and "cannot open display :0.0". If I quit awesome/X and login again(without reboot) all works just fine. Could you please help me to solve this problem? Thank you in advance.
Edit: found this in the Xorg.0.log:
[ 164.412] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 15 11:47:28 2012
[ 164.412] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 164.413] (==) No Layout section. Using the first Screen section.
[ 164.413] (==) No screen section available. Using defaults.
[ 164.413] (**) |-->Screen "Default Screen Section" (0)
[ 164.413] (**) | |-->Monitor "<default monitor>"
[ 164.413] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
Last edited by ArtemGuzhva (2012-06-18 07:46:12)

Okay, it is working fine now I have uninstalled initscripts and installed sysvcompat.
NOTE: before uninstalling initscripts and sysvinit, reboot your computer with init=/bin/systemd in your kernel cmdline, because you will not be able to shutdown properly due to the lack of inittab.
Last edited by ArtemGuzhva (2012-06-18 07:49:12)

Systemd kills my network on shutdown before nfs is unmounted

My home-directory is on nfs and I've been having this issue for a couple of months now; when shutting down systemd will stop my network without waiting for nfs unmounts to complete This results in incomplete shutdowns which sometimes take more then 10 minutes. It looks like this:
Nov 15 10:52:26 desktop systemd[1]: Stopped RPC GSS-API client-side daemon.
Nov 15 10:52:26 desktop systemd[1]: Unmounting RPC pipe filesystem...
Nov 15 10:52:26 desktop systemd[1]: Stopping RPC Bind...
Nov 15 10:52:26 desktop rpcbind[454]: rpcbind terminating on signal. Restart with "rpcbind -w"
Nov 15 10:52:26 desktop rpcbind[454]: cannot open file = /run/rpcbind.xdr for writing
Nov 15 10:52:26 desktop rpcbind[454]: cannot save any registration
Nov 15 10:52:26 desktop rpcbind[454]: cannot open file = /run/portmap.xdr for writing
Nov 15 10:52:26 desktop rpcbind[454]: cannot save any registration
Nov 15 10:52:26 desktop systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 15 10:52:26 desktop systemd[1]: Stopped RPC Bind.
Nov 15 10:52:26 desktop systemd[1]: Unit rpcbind.service entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Stopped Login Service.
Nov 15 10:52:26 desktop umount[3604]: umount: /home/user: not mounted
Nov 15 10:52:26 desktop systemd[1]: home-user.mount mount process exited, code=exited status=32
Nov 15 10:52:26 desktop systemd[1]: Unmounted /home/user.
Nov 15 10:52:26 desktop systemd[1]: Unit home-user.mount entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Unmounted RPC pipe filesystem.
Nov 15 10:52:26 desktop systemd[1]: mnt-bigdisk.mount mount process exited, code=exited status=32
Nov 15 10:52:26 desktop systemd[1]: Unmounted /mnt/bigdisk.
Nov 15 10:52:26 desktop systemd[1]: Unit mnt-bigdisk.mount entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Stopping Network is Online.
Nov 15 10:52:26 desktop systemd[1]: Stopped target Network is Online.
Nov 15 10:52:26 desktop systemd[1]: Stopping Network.
Nov 15 10:52:26 desktop systemd[1]: Stopped target Network.
Nov 15 10:52:26 desktop systemd[1]: Stopping dhcpcd on enp3s0...
Nov 15 10:52:26 desktop umount[3605]: umount: /mnt/bigdisk: not mounted
Nov 15 10:52:26 desktop dhcpcd[3623]: dhcpcd[3623]: sending signal 15 to pid 414
Nov 15 10:52:26 desktop dhcpcd[3623]: dhcpcd[3623]: waiting for pid 414 to exit
Nov 15 10:52:26 desktop dhcpcd[3623]: sending signal 15 to pid 414
Nov 15 10:52:26 desktop dhcpcd[3623]: waiting for pid 414 to exit
Nov 15 10:52:26 desktop dhcpcd[414]: received SIGTERM from PID 3623, stopping
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: removing interface
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: deleting host route to 192.168.1.12 via 127.0.0.1
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: deleting route to 192.168.1.0/24
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: deleting default route via 192.168.1.254
Nov 15 10:52:26 desktop systemd[1]: Stopped User Manager for 1000.
Nov 15 10:52:26 desktop systemd[1]: Stopping user-1000.slice.
Nov 15 10:52:26 desktop systemd[1]: Removed slice user-1000.slice.
Nov 15 10:52:26 desktop dhcpcd[414]: exited
Nov 15 10:52:26 desktop systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Nov 15 10:52:26 desktop systemd[1]: Stopped dhcpcd on enp3s0.
Nov 15 10:52:26 desktop systemd[1]: Unit [email protected] entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Stopping system-dhcpcd.slice.
Nov 15 10:52:26 desktop systemd[1]: Removed slice system-dhcpcd.slice.
Nov 15 10:52:27 desktop systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
Nov 15 10:52:27 desktop systemd[1]: Stopped SLiM Simple Login Manager.
Nov 15 10:52:27 desktop systemd[1]: Unit slim.service entered failed state.
Nov 15 10:52:27 desktop systemd[1]: Stopping Permit User Sessions...
Nov 15 10:52:27 desktop systemd[1]: Stopping Local File Systems.
Nov 15 10:52:27 desktop systemd[1]: Stopped target Local File Systems.
Nov 15 10:52:27 desktop systemd[1]: Unmounting /home...
Nov 15 10:52:27 desktop systemd[1]: Unmounting /var/backup...
Nov 15 10:52:27 desktop systemd[1]: Unmounting /tmp...
Nov 15 10:52:27 desktop umount[3666]: umount: /home: target is busy
Nov 15 10:52:27 desktop umount[3666]: (In some cases useful info about processes that
Nov 15 10:52:27 desktop umount[3666]: use the device is found by lsof(8) or fuser(1).)
Nov 15 10:52:27 desktop systemd[1]: home.mount mount process exited, code=exited status=32
Nov 15 10:52:27 desktop systemd[1]: Failed unmounting /home.
Nov 15 10:52:27 desktop systemd[1]: Unmounted /tmp.
Nov 15 10:52:27 desktop systemd[1]: Unmounted /var/backup.
Nov 15 10:52:27 desktop systemd[1]: Starting Unmount All Filesystems.
Nov 15 10:52:27 desktop systemd[1]: Reached target Unmount All Filesystems.
Nov 15 10:52:27 desktop systemd[1]: Stopping Local File Systems (Pre).
Nov 15 10:52:27 desktop systemd[1]: Stopped target Local File Systems (Pre).
Nov 15 10:52:27 desktop systemd[1]: Stopping Remount Root and Kernel File Systems...
Nov 15 10:52:27 desktop systemd[1]: Stopped Remount Root and Kernel File Systems.
Nov 15 10:52:27 desktop systemd[1]: Starting Shutdown.
Nov 15 10:52:27 desktop systemd[1]: Reached target Shutdown.
Nov 15 10:52:27 desktop systemd[1]: Starting Final Step.
Nov 15 10:52:27 desktop systemd[1]: Reached target Final Step.
Nov 15 10:52:27 desktop systemd[1]: Starting Reboot...
Nov 15 10:52:27 desktop systemd[1]: Shutting down.
Nov 15 10:52:27 desktop sudo[3600]: pam_unix(sudo:session): session closed for user root
Nov 15 10:52:27 desktop systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Nov 15 10:52:27 desktop systemd[1]: Set hardware watchdog to 10min.
Nov 15 10:52:27 desktop kernel: watchdog watchdog0: watchdog did not stop!
Nov 15 10:52:27 desktop systemd-journal[144]: Journal stopped
Does systemd have any notion of a relation between the network connection and the filesystem that is mounted via that connection? Because it seems to treat the filesystem equal to a local filesystem which it clearly isn't.

Relevant parts:
/dev/sda2 / ext4 defaults,discard 0 1
none /tmp tmpfs nodev,nosuid,noatime,size=4G,mode=1777
/dev/md1 /home ext4 defaults 0 3
server:/var/cache/pacman /var/cache/pacman nfs4 exec,auto
server:/srv /srv nfs4 defaults,auto
server:/home/user /home/user nfs4 exec,auto
Last edited by Spider.007 (2013-11-23 12:46:19)

How im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

how im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

What "auto shutdown problem" are you talking about?

Clock problem and shutdown problem! Are they related?

Having a problem with my Dual 2 GHz Power Mac G5
A few days ago I noticed that my clock was not showing in the menu bar in the upper right corner of my desktop.
I went into System Preferences and went to Date & Time. Under the clock tab “Show Date and Time in Menu Bar” the box was not checked off. I checked it off and went to the “Date and Time” tab. The date and time was correct. I then checked the box “Click the lock to prevent further changes” to lock it. The date and time did not show up in the menu bar. I then went back to the tab “Show Date and Time in Menu Bar” and the box I checked was not checked off even thought the lock was still locked.
I then moved my cursor up to the menu bar in the upper right corner to see what would happen and the spinning beach ball started up but only for the original icons such as Bluetooth, Mobile Me (which I do not use), Time Machine, Spaces (doesn’t indicated the number when I switch Spaces, etc. The icons Norton Anti Virus and Tech Tool Pro in the menu bar are okay.
Also, when I attempt to shut down my computer the system clears the icons from my desktop except for a picture I have on my desktop and I get a gray wheel spinning and the system just hangs until I press and hold the on/off switch. I don’t know if the clock and shutdown problems are related.
The only new software I loaded recently was Skype with Logitech WebCam for the Mac and Quicken 2007 (Had a problem with Quicken 2006). They both are working okay.
And ideas on why I cannot get my clock to show up and my computer to shutdown?

You may have to consider a new post in the Hardware forum area for the computer
model and build/year; if there is a possibility of some basis the matter could be in
the machine and not the software running within it.
Your last two/three posts are in the Leopard 10.5(.8) forum area and do indicate
some kind of problem where troubleshooting the computer to discover if the matter
at hand would be either hardware or software based, may be the way to go.
The link to the 10.6 Snow Leopard forum won't be of help if your computer is a
PPC-based G5 tower, or other older pre-Intel configuration. And I remember
your earlier questions about the iMac G4 and some other issues in the past.
You may ask the moderators to put your post in a new thread of its own, in the
Leopard 10.5 area; so as to not 'piggy-back' another topic; even though some
of the odd issues you've had seem similar to this OP's topic line and appear to
be in the same general series of hardware. {The question here seems valid.}
The routine suggestions to check, test, verify, and perhaps repair or replace
the system; save a bootable clone to suitable external standalone device if
testing a suspect computer's viability is recommended; and the basics if not
already tried to help isolate the issue(s) as you've posted elsewhere, may be
of some help to try and do; so in that matter, a new thread of your own is best
for your own directed feedback. Since this kind of advice applies to most any
situation, including troubleshooting what may be hardware or software, I'm
adding my two and three-tenths cents worth here.
Your original included Apple Hardware Test may be of some help, in the process
of elimination; but is not conclusive, so other methods would be also suggested.
Some ideas appear to cover the same ground. However, system corruption or
disc failure can also manifest itself in odd ways & affect things indirectly for a time.
• OS X Maintenance And Troubleshooting
http://www.macattorney.com/ts.html
• Mac OS X BASIC TROUBLESHOOTING & MAINTENANCE
http://www.gballard.net/macrant/osx_troubleshooting.html
• Troubleshooting Tips for computers:
http://www.stcdio.org/offices/cem/mediaandtechnology/cem-computer-classes/troubl eshooting.html
So, at the risk of inadvertently alienating the OP, I am posting this as
a general help to following readers at some later time; and it may not
be too simple for a refresh course.
Some software issues can be resolved by repairing disk permissions,
and re-applying the last OS X update Combo file over the same one
already in the system; or if not up-to-date already, check & repair all
the general items and then apply the last Combo update.
A too-full hard disk drive can compromise the system integrity, so that
is a matter of course to keep up on what resources exist and remain
for the OS X to function correctly and for apps to multi-task together.
However that works out...
Good luck & happy computing!

Ypbind, systemd and net-auto-wired problems

I have the following problem after boot:
YPBINDPROC_DOMAIN: Domain not bound
And can't login with any user!
I have to restart the ypbind so I can login.
I am using systemd and net-auto-wired.service to start my connection.
I think the problem is that the ypbind.service is being started before the network.
# journalctl | grep ypbind
Feb 10 14:36:00 qomplex000 ypbind[369]: Host name lookup failure
I can't find the problem, tried all kinds of configurations on
/usr/lib/systemd/system/ypbind.service
And no change.
I think there is a relation with this:
https://bugzilla.redhat.com/show_bug.cgi?id=632620

oangelo wrote:One can use the words "before" and "after", on *.sevice files, to make sure that the service will start on the right order.
But this does check only start but not completion of the started service. In our case dns is started and systemd moves on, not waiting for a valid dns configuration (but it takes a few seconds for dhcpd to put the nameserver in /etc/resolv.conf). The ypbind service gets started and tries to resolve a dns for ypserver from /var/yp.conf. Since the nameserver is not configured properly at this moment it gets no valid answer. Unfortunately ypbind seems not to be smart enough to retry ypserver and hangs. Thats the cause for 'YPBINDPROC_DOMAIN: Domain not bound'.
From the ypbind manpage:
This ypbind version listens for DBUS messages from NetworkManager. If no NetworkManager is running at startup, ypbind will behave as usual and assumes there is a working network connection. If NetworkManager is running on the system, ypbind will only search and provide NIS informations, if NetworkManager tells that a network connection is available. If NetworkManager establishes a connection, ypbind will reread all configuration files, registers at the local portmapper and try to search NIS servers. If NetworkManager drops a connection, ypbind will unregister from portmapper.
I don't use NetworkManager on these systems (because of keeping it simple, as a real archer).
Harvey

Systemd takes 100% of a single thread and will not allow shutdown

A few systemd updates ago I started to have this problem. On update, systemd takes up 100% of one of my four threads (switching theads on every so often according to Conky) and will not let me reboot properly. If I run "sudo poweroff" it broadcasts that the system is going down then just doesn't. No amount of waiting after the update is finished sees systemd finish whatever it's atempting to do.
Holding the power button to force the computer off causes it to be unbootable. The system hangs as it checks the file system. No amount of waiting sees the file system check completed.
So far the only "fix" that I've found is to load the system up in a ch-root environment and roll systemd back.
I really don't know enough to fix this myself and google searches have turned up seemingly similar problems who's fixes don't work in my case.

Stebalien wrote:
Anything in dmesg after updating? When you reboot, try replacing the quiet command line argument with verbose and see where systemd actually stops. Also, immediately after updating, try attaching strace to it (strace -p 1) and logging the output.
Regardless, this really sounds like a bug.
I couldn't find anything in dmesg. I grepped "systemd" and nothing strange showed up.
When booting verbosely the system prints "Welcome to Arch Linux" then hangs.
The newest installation media does the same thing so I'm going to have to find an older one to roll the package back. It doesn't hang on my laptop so it must be an issue with this netbook.
I couldn't find anything about systemd having issues with the atom N2600 and it's not old hardware so I doubt they've just dropped support.
Last edited by Deyna (2013-12-24 05:54:22)

Usb ports and shutdown problem

hi
im using win xp with bootcamo on my macbook 13"
sometimes i close the lid while xp still running.
when i open it, i cant use any of the usb ports....i have to restart in order to use the usb port again. and that brings me to another problem - the computer get stuck in the "logging off" screen...i need to press the power button for a couple of seconds, and then turn it on again....
so, usb not working and computer freeze on shutdown....
help anyone??
thanks

In Vista, you can go into Power Options control panel and change how and when devices, like USB, will go into low power mode or not.
Of course better drivers could help, too.
At this point, I would clean up and repair the drive; make sure you have a good image (WinClone).
Along with chkdsk there is system file checker that will look for some types of errors
sfc /scannow
But it sounds like the hard restarts have a toll in the file system's integrity.

A665-s6094 starting from sleep problem/hibernate problem and starting form shutdown problem

hey i have a 2 day old toshiba a665-s6094 laptop and whenever i put it to sleep(as in closing the screen not from the button nor the start menu) it cant start again so i have to remove and put back the battery for it to work.
Also it on hibernate, only the display turns off and it doesnt hibernate.
and i have the same problem with shutdown, sometimes doesnt start after shutdown, and only removing the battery and putting it back in makes it start.
Any help would be appreciated.

I am 99% sure that you have the option set to require a password when waking from sleep. If that's the case, the Mac will go back to sleep after a few minutes if no password is entered on wake.
Two workarounds:
1) Turn off the password-on-wake preference, or:
2) Fast-user-switch to the login window before sleeping your Mac. When it wakes it will stay awake; and you still have the security of needing a password to get back into your user account.
Message was edited by: Király

Start up Problem and unresponsive apps or shutdown , restart always loading

i have MacBook 13 inch mid 2012
processor 2.9 Ghz intel core i7
memory 8GB 1600 mhz DDR3
OS x Yosemite V 10.10.2
i did an up date from app store and now can't start up my os x its work slowly if will open apps unresponsive always loading.
i did reinstall os x and not working again.
i did go through Safe Boot its work but when restart again os x not start up or if its work apps unresponsive and keep loading.
cant shutdown normaly or restart normal just through holding power Push for few seconde.
how i nee to fix this?

If the safe boot worked well and a restart produced the same adverse symptoms suggests a problem caused by a third party application. If you delete all third party items and reinstall them systematically, you might be able to find the 'trouble maker'.
Ciao.

[zfs] doesn't unmount at shutdown

I ve done the tutorial fr installing zfs on archlinux as a root system but i still have some problem.
I've used that one :
https://wiki.archlinux.org/index.php/In … nux_on_ZFS
When i boot my computer i have the emergency bash and i must import / export my pool.
I've already done :
systemctl enable zfs.service
here is my /usr/lib/systemd/system/zfs.service :
[Unit]
Description=Zettabyte File System (ZFS)
Documentation=man:zfs(8) man:zpool(8)
DefaultDependencies=no
After=cryptsetup.target
Before=local-fs.target
Conflicts=shutdown.target umount.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/modprobe zfs
#ExecStart=/usr/bin/zpool import -c /etc/zfs/zpool.cache -aN
#ExecStart=/usr/bin/zfs mount -a
#ExecStart=/usr/bin/zfs share -a
ExecStop=/usr/bin/swapoff -a
ExecStop=/usr/bin/zfs umount -a
ExecStop=/usr/bin/zpool export zroot
[Install]
WantedBy=local-fs.target
and here is a journalctl --unit=zfs
-- Logs begin at Sun 2013-09-15 08:49:49 CEST, end at Mon 2013-09-16 09:53:19 CEST. --
Sep 15 08:58:21 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 15 09:01:18 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 15 09:04:44 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
Sep 15 09:06:09 Kusanagi systemd[1]: Stopping Zettabyte File System (ZFS)...
[1;39m-- Reboot --[0m
Sep 15 09:08:28 Kusanagi systemd[1]: zfs.service: main process exited, code=exited, status=1/FAILURE
Sep 15 09:08:28 Kusanagi systemd[1]: Failed to start Zettabyte File System (ZFS).
Sep 15 09:08:28 Kusanagi systemd[1]: Unit zfs.service entered failed state.
[1;39m-- Reboot --[0m
Sep 15 09:33:54 Kusanagi zpool[416]: failed to open cache file: No such file or directory
Sep 15 09:33:54 Kusanagi systemd[1]: zfs.service: main process exited, code=exited, status=1/FAILURE
Sep 15 09:33:54 Kusanagi systemd[1]: Failed to start Zettabyte File System (ZFS).
Sep 15 09:33:54 Kusanagi systemd[1]: Unit zfs.service entered failed state.
[1;39m-- Reboot --[0m
Sep 15 10:15:54 Kusanagi systemd[1]: [/usr/lib/systemd/system/zfs.service:18] Missing '='.
Sep 15 10:18:34 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:32:12 Kusanagi systemd[1]: [/usr/lib/systemd/system/zfs.service:18] Missing '='.
Sep 15 10:32:18 Kusanagi systemd[1]: [/usr/lib/systemd/system/zfs.service:18] Missing '='.
Sep 15 10:37:06 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:48:19 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:49:12 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:49:33 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:49:54 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:50:22 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:51:16 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:51:44 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:51:53 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:53:38 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:53:44 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:56:40 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 11:00:45 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 11:05:38 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 11:12:32 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
[1;39m-- Reboot --[0m
Sep 15 22:05:17 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 16 05:55:32 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 16 07:33:39 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
and here is a systemctl status zfs.service :
systemctl status zfs.service
zfs.service - Zettabyte File System (ZFS)
Loaded: loaded (/usr/lib/systemd/system/zfs.service; enabled)
Active: active (exited) since Mon 2013-09-16 07:33:39 CEST; 2h 47min ago
Docs: man:zfs(8)
man:zpool(8)
Process: 405 ExecStart=/sbin/modprobe zfs (code=exited, status=0/SUCCESS)
Sep 16 07:33:39 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
and i've already done a # systemctl daemon-reload
Any idea ?
regards
Bussiere

seiichiro0185 wrote:
I had this problem too in the beginning, but did solve it by setting the hostid like this:
~# hostid > /etc/hostid
After this I rebuilt my initrd with
~# mkinitcpio -p linux
After these two steps I could remove the zfs_force from my kernel line and it works without a problem since then.
This solution f*******ed up my installation and now i'am have a real pain to reinstall my system because there is a version problem with the zfs module :
https://bbs.archlinux.org/viewtopic.php … 0#p1331360
And it may also have f***ed up my dd.
Bussiere

Systemd and samba

Hello
So i have decided to install systemd and so far is working great and i am just getting to know it. I have one problem - i disabled smbd.service but samba is somehow enabled (tough systemd is not showing samba as enabled) because i can reach other Windows computer. What is the trick?
systemctl -t service
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
acpid.service loaded active running ACPI event daemon
console-kit-daemon.service loaded active running Console Manager
console-kit...system-start.service loaded active exited Console System Startup Logging
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kdm.service loaded active running K Display Manager
laptop-mode-tools.service loaded active exited Laptop Power Saving Tools
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Servi
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-remount-fs.service loaded active exited Remount Root and Kernel File System
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directo
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
ufw.service loaded active exited CLI Netfilter Manager
upower.service loaded active running Daemon for power management
wicd.service loaded active running Wicd a wireless and wired network
systemctl -t socket
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
acpid.socket loaded active listening ACPID Listen Socket
dbus.socket loaded active running D-Bus System Message Bus Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-udevd-control.socket loaded active listening udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
7 units listed. Pass --all to see inactive units, too.
systemctl -t target
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
13 units listed. Pass --all to see inactive units, too.
Thanks!

Hi
I can't find anything useful, maybe you can help:
systemd-cgls
├ user
│ └ saso
│ └ c1
│ ├ 922 -:0
│ ├ 1039 /bin/sh /usr/bin/startkde
│ ├ 1061 /usr/bin/dbus-launch --sh-syntax --exit-with-session
│ ├ 1062 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
│ ├ 1068 /usr/bin/pulseaudio --start
│ ├ 1087 /usr/lib/pulse/gconf-helper
│ ├ 1089 /usr/lib/GConf/gconfd-2
│ ├ 1110 /usr/bin/gpg-agent -s --daemon --pinentry-program /usr/bin/pinentry-qt4 --writ...
│ ├ 1113 /usr/bin/ssh-agent -s
│ ├ 1127 /usr/lib/kde4/libexec/start_kdeinit +kcminit_startup
│ ├ 1128 kdeinit4: kdeinit4 Running...
│ ├ 1129 kdeinit4: klauncher [kdeinit] --fd=9
│ ├ 1131 kdeinit4: kded4 [kdeinit]
│ ├ 1157 kdeinit4: kglobalaccel [kdeinit]
│ ├ 1165 kwrapper4 ksmserver
│ ├ 1166 kdeinit4: ksmserver [kdeinit]
│ ├ 1192 kwin -session 1011413c144df000134217689000000241270000_1343549886_678034
│ ├ 1210 /usr/bin/kactivitymanagerd
│ ├ 1241 /usr/bin/knotify4
│ ├ 1244 kdeinit4: krunner [kdeinit]
│ ├ 1246 kdeinit4: plasma-desktop [kdeinit]
│ ├ 1259 /usr/bin/kuiserver
│ ├ 1295 kdeinit4: kaccess [kdeinit]
│ ├ 1309 /usr/bin/kwrited
│ ├ 1352 /usr/bin/colibri -session 1011413c144df000134217689800000241270019_1343549886_...
│ ├ 1364 kdeinit4: kmix [kdeinit] -session 1011413c144df000134351262700
│ ├ 1402 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
│ ├ 1418 firefox
│ ├ 1421 syndaemon -t -k -i 1 -d
│ ├ 1422 /bin/sh /home/saso/.kde4/Autostart/pim.sh
│ ├ 1423 /bin/bash /home/saso/.kde4/Autostart/temperatura.sh
│ ├ 1680 kdeinit4: kwalletd [kdeinit]
│ ├ 7777 /usr/bin/kontact
│ ├ 7785 /usr/bin/akonadi_control
│ ├ 7787 akonadiserver
│ ├ 7789 /usr/bin/mysqld --defaults-file=/home/saso/.local/share/akonadi/mysql.conf --d...
│ ├ 7830 /usr/bin/akonadi_calendarsearch_agent --identifier akonadi_calendarsearch_agen...
│ ├ 7831 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_res...
│ ├ 7832 /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource akonadi_kalarm_resourc...
│ ├ 7833 /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource akonadi_kalarm_resourc...
│ ├ 7834 /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource akonadi_kalarm_resourc...
│ ├ 7835 /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resou...
│ ├ 7836 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agen...
│ ├ 7837 /usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent
│ ├ 7838 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
│ ├ 7839 /usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_11
│ ├ 7840 /usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_6
│ ├ 7841 /usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_7
│ ├ 7842 /usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_9
│ ├ 7885 /usr/bin/nepomukserver
│ ├ 11725 /usr/lib/firefox/plugin-container /usr/lib/mozilla/plugins/libflashplayer.so -...
│ ├ 11946 sleep 120s
│ ├ 11992 sleep 50s
│ ├ 12007 kdeinit4: konsole [kdeinit]
│ ├ 12009 /bin/bash
│ ├ 12017 systemd-cgls
│ └ 12018 less
└ system
├ 1 /sbin/init
├ upower.service
│ └ 1160 /usr/lib/upower/upowerd
├ rtkit-daemon.service
│ └ 1069 /usr/lib/rtkit-daemon
├ console-kit-daemon.service
│ └ 962 /usr/sbin/console-kit-daemon --no-daemon
├ kdm.service
│ ├ 308 /usr/bin/kdm -nodaemon
│ └ 320 /usr/bin/X :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-8CfcFa
├ [email protected]
│ └ tty1
│ └ 307 /sbin/agetty --noclear tty1 38400
├ dbus.service
│ ├ 297 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-...
│ ├ 1029 /usr/lib/polkit-1/polkitd --no-debug
│ ├ 1200 /usr/lib/udisks/udisks-daemon
│ └ 1201 udisks-daemon: not polling any devices
├ systemd-logind.service
│ └ 296 /usr/lib/systemd/systemd-logind
├ acpid.service
│ └ 293 /usr/sbin/acpid -f
├ wicd.service
│ ├ 291 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py --no-daemon
│ ├ 919 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
│ ├ 9861 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/00226b5630fc -Dwext
│ └ 9894 /usr/sbin/dhcpcd -h saso-laptop --noipv4ll wlan0
├ systemd-journald.service
│ └ 103 /usr/lib/systemd/systemd-journald
└ systemd-udevd.service
└ 95 /usr/lib/systemd/systemd-udevd
EDIT: I think it has something with KDE. When i through Dolphin reach Windows machine i can see this through systemd-cgls:
12480 kdeinit4: kio_smb [kdeinit] smb local:/tmp/ksocket-saso/klaunc...
But this disappear when i close Dolphin.
Last edited by Shark (2012-07-29 15:36:31)

Systemd and nm_dispatcher (on remote shares)

Hi,
On my laptop I'm using systemd and networkmanager, like many of you I suppose.
I have an NFS-server setup at home and one at work, so I would prefer to only connect to the NFS-server within my reach and not send out credentials into the wild when the other NFS-server is not around. I thought that nm_dispatcher is the perfect solution and I wrote a script that accomplishes this with the sysV initscripts.
Now I'm using systemd and my laptop won't shutdown anymore: it hangs at unmounting my disks.
I guess the nm_dispatcher-script to unmount the NFS-exports is never run, and so the NFS-exports are never unmounted.
Questions:
1. Is this the expected behaviour or is this a bug somewhere?
2. Can systemd do this natively? I know it is able to mount remote shares, but can you also specify that the mount should only be tried if connected to a specific SSID?
THX!
Last edited by zenlord (2012-08-23 11:31:34)

Sharepoints is not needed in your case, it's for controlling what "other" Isers can access.
Logging into the Remote one with the Remote one's User &PW gives you the samr rights as being there and logging onto it!

Systemd and cifs unmount at shutdown problem

Similar Messages

Maybe you are looking for