/run Directory

Hi,

My Fedora 21 system is fsck'ing every time when it boots. Below is the boot.log:

Code:

[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
[  OK  ] Found device ST9500325AS 11.
          Starting File System Check on /dev/disk/by-uuid/f6256ca7-5d1a-4fe4-aab8-91ed70ea48bd... 
[  OK  ] Found device ST9500325AS 10.
 [    3.823843] systemd-fsck[319]: /dev/sda11: clean, 249123/4653056 files, 4411466/18611712 blocks 
[  OK  ] Started dracut initqueue hook.
         Starting dracut pre-mount hook...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Started File System Check on /dev/disk/by-uuid/f6256ca7-5d1a-4fe4-aab8-91ed70ea48bd.
[  OK  ] Started dracut pre-mount hook.
         Mounting /sysroot...
[  OK  ] Mounted /sysroot.
[  OK  ] Reached target Initrd Root File System.
         Starting Reload Configuration from the Real Root...
[  OK  ] Started Reload Configuration from the Real Root.
[  OK  ] Reached target Initrd File Systems.
[  OK  ] Reached target Initrd Default Target.
         Starting dracut pre-pivot and cleanup hook...
[  OK  ] Started dracut pre-pivot and cleanup hook.
         Starting Cleaning Up and Shutting Down Daemons...
         Stopping Cleaning Up and Shutting Down Daemons...
[  OK  ] Stopped target Timers.
         Starting Plymouth switch root service...
[  OK  ] Stopped Cleaning Up and Shutting Down Daemons.
         Stopping dracut pre-pivot and cleanup hook...
[  OK  ] Stopped dracut pre-pivot and cleanup hook.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
         Stopping dracut pre-mount hook...
[  OK  ] Stopped dracut pre-mount hook.
         Stopping dracut initqueue hook...
[  OK  ] Stopped dracut initqueue hook.
[  OK  ] Stopped target Initrd Default Target.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Slices.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Sockets.
[  OK  ] Stopped target System Initialization.
         Stopping Apply Kernel Variables...
[  OK  ] Stopped Apply Kernel Variables.
         Stopping udev Coldplug all Devices...
[  OK  ] Stopped udev Coldplug all Devices.
[  OK  ] Stopped target Swap.
[  OK  ] Stopped target Local File Systems.
         Stopping udev Kernel Device Manager...
[  OK  ] Stopped udev Kernel Device Manager.
         Stopping dracut pre-udev hook...
[  OK  ] Stopped dracut pre-udev hook.
         Stopping dracut cmdline hook...
[  OK  ] Stopped dracut cmdline hook.
         Stopping Create Static Device Nodes in /dev...
[  OK  ] Stopped Create Static Device Nodes in /dev.
         Stopping Create list of required static device nodes for the current kernel...
[  OK  ] Stopped Create list of required static device nodes for the current kernel.
[  OK  ] Closed udev Kernel Socket.
[  OK  ] Closed udev Control Socket.
         Starting Cleanup udevd DB...
[  OK  ] Started Cleanup udevd DB.
[  OK  ] Reached target Switch Root.
[  OK  ] Started Plymouth switch root service.
         Starting Switch Root...

Welcome to Fedora 21 (Twenty One)!

[  OK  ] Stopped Switch Root.
[  OK  ] Stopped target Switch Root.
[  OK  ] Stopped target Initrd File Systems.
         Stopping File System Check on /dev/disk/by-uuid/f6256ca7-5d1a-4fe4-aab8-91ed70ea48bd...
[  OK  ] Stopped File System Check on /dev/disk/by-uuid/f6256ca7-5d1a-4fe4-aab8-91ed70ea48bd.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Stopped target Initrd Root File System.
[  OK  ] Reached target User and Group Name Lookups.
         Starting Replay Read-Ahead Data...
         Starting Collect Read-Ahead Data...
[  OK  ] Created slice system-getty.slice.
[  OK  ] Reached target Login Prompts.
[  OK  ] Created slice User and Session Slice.
[ INFO ] PNFS blkmaping enablement. is not active.
[DEPEND] Dependency failed for pNFS block layout mapping daemon.
         Mounting RPC Pipe File System...
[  OK  ] Reached target Slices.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
         Mounting Debug File System...
         Mounting Huge Pages File System...
[  OK  ] Set up automount Arbitrary Executable File Formats File System Automount Point.
[  OK  ] Stopped Flush Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
         Mounting POSIX Message Queue File System...
         Starting Create list of required static device nodes for the current kernel...
[  OK  ] Listening on Device-mapper event daemon FIFOs.
[  OK  ] Listening on LVM2 metadata daemon socket.
         Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on udev Control Socket.
         Starting udev Coldplug all Devices...
         Expecting device dev-disk-by\x2duuid-b32aee65\x2d0b57\x2d4b0e\x2dab00\x2d0c87d86da48b.device...
         Mounting Temporary Directory...
[  OK  ] Started Collect Read-Ahead Data.
[  OK  ] Started Replay Read-Ahead Data.
         Starting File System Check on Root Device...
         Starting Apply Kernel Variables...
[  OK  ] Started Create list of required static device nodes for the current kernel.
[  OK  ] Started udev Coldplug all Devices.
         Starting udev Wait for Complete Device Initialization...
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Temporary Directory.
         Starting LVM2 metadata daemon...
[  OK  ] Started LVM2 metadata daemon.
[  OK  ] Started Journal Service.
 [   10.934370] systemd-fsck[421]: /dev/sda11: Superblock last write time is in the future.
[   10.936407] systemd-fsck[421]: (by less than a day, probably due to the hardware clock being incorrectly set).  FIXED. 
[  OK  ] Mounted RPC Pipe File System.
[  OK  ] Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
 [   37.171839] systemd-fsck[421]: /dev/sda11: 249123/4653056 files (0.4% non-contiguous), 4411466/18611712 blocks 
[  OK  ] Started File System Check on Root Device.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting Import network configuration from initramfs...
         Starting Configure read-only root support...
         Starting Flush Journal to Persistent Storage...
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Configure read-only root support.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Import network configuration from initramfs.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting NFSD configuration filesystem...
[  OK  ] Mounted NFSD configuration filesystem.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started udev Wait for Complete Device Initialization.
         Starting Activation of DM RAID sets...
[  OK  ] Started Activation of DM RAID sets.
[  OK  ] Reached target Local File Systems.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Created slice system-systemd\x2dbacklight.slice.
         Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...
[  OK  ] Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[  OK  ] Reached target Sound Card.
[  OK  ] Found device ST9500325AS 10.
         Activating swap /dev/disk/by-uuid/b32aee65-0b57-4b0e-ab00-0c87d86da48b...
[  OK  ] Activated swap /dev/disk/by-uuid/b32aee65-0b57-4b0e-ab00-0c87d86da48b.
[  OK  ] Reached target Swap.
[  OK  ] Created slice system-systemd\x2drfkill.slice.
         Starting Load/Save RF Kill Switch Status of rfkill0...
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Security Auditing Service...
[  OK  ] Started Security Auditing Service.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on Open-iSCSI iscsid Socket.
[  OK  ] Listening on CUPS Printing Service Sockets.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on Open-iSCSI iscsiuio Socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Paths.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Timers.
         Starting Manage Sound Card State (restore and store)...
[  OK  ] Started Manage Sound Card State (restore and store).
[  OK  ] Reached target Basic System.
         Starting Accounts Service...
         Starting RealtimeKit Scheduling Policy Service...
         Starting Preprocess NFS configuration...
         Starting GSSAPI Proxy Daemon...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Machine Check Exception Logging Daemon...
         Starting NTP client/server...
         Starting Modem Manager...
         Starting Hardware RNG Entropy Gatherer Daemon...
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
         Starting Rollback uncommitted netcf network config change transactions...
         Starting Login Service...
         Starting D-Bus System Message Bus...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started RealtimeKit Scheduling Policy Service.
         Starting firewalld - dynamic firewall daemon...
         Starting LSB: Init script for live image....
[  OK  ] Started Preprocess NFS configuration.
[  OK  ] Started GSSAPI Proxy Daemon.
[  OK  ] Started Machine Check Exception Logging Daemon.
[  OK  ] Started Rollback uncommitted netcf network config change transactions.
[  OK  ] Started NTP client/server.
[  OK  ] Started LSB: Init script for live image..
         Starting ABRT Automated Bug Reporting Tool...
[  OK  ] Started ABRT Automated Bug Reporting Tool.
         Starting ABRT kernel log watcher...
[  OK  ] Started ABRT kernel log watcher.
         Starting Install ABRT coredump hook...
         Starting SYSV: Late init script for live image....
[  OK  ] Started Login Service.
[  OK  ] Started Install ABRT coredump hook.
[  OK  ] Started SYSV: Late init script for live image..
         Starting Authorization Manager...
[  OK  ] Started Authorization Manager.
[  OK  ] Started Accounts Service.
[  OK  ] Started Modem Manager.
[  OK  ] Started firewalld - dynamic firewall daemon.
         Starting Network Manager...
[  OK  ] Started Network Manager.
         Starting Network Manager Wait Online...
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network.
         Starting Notify NFS peers of a restart...
         Starting Virtualization daemon...
[  OK  ] Reached target Network is Online.
[  OK  ] Started Notify NFS peers of a restart.
[  OK  ] Reached target NFS client services.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting Permit User Sessions...
[  OK  ] Started Permit User Sessions.
         Starting GNOME Display Manager...
         Starting Command Scheduler...
[  OK  ] Started Command Scheduler.
         Starting Job spooling tools...
[  OK  ] Started Job spooling tools.
         Starting Wait for Plymouth Boot Screen to Quit...
[  OK  ] Started GNOME Display Manager.

I have already synced the time with hardware clock.

Any light?

Thanks.

I have SLES 11.3 (x86_64).
When I try to connect to this server via ssh or console without kde everything is OK.
But when I try to connect to this server through kde, in /var/log/messages I can see:

Mar 25 10:03:04 server1 kdm: :0[6560]: Cannot open ConsoleKit session: Unable to open session: Failed to execute program /lib64/dbus-1/dbus-daemon-launch-helper: Success
Mar 25 10:03:04 server1 kdm: :0[6560]: Client start failed
Mar 25 10:03:04 server1 kdm: :0[6560]: Cannot close ConsoleKit session: Unable to close session: no session open

# ls -l /lib64/dbus-1/dbus-daemon-launch-helper
-rwsr-x--- 1 root messagebus 47912 Oct 15 2012 /lib64/dbus-1/dbus-daemon-launch-helper

Can you help me to resolve my problem?

Hello

I want to share a folder on my Fedora linux pc with a Windows 8 pc in the same network.

I have followed this guide : http://www.labtestproject.com/config...rver_on_fedora

but I am not able to see my share on my Fedora linux pc from the other Windows 8 PC.

This is my /etc/samba/smb.conf :

Code:

[global]
        workgroup = mygroup
        server string = HP Samba
;       netbios name = MYSERVER

;       interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
;       hosts allow = 127. 192.168.12. 192.168.13.

;       max protocol = SMB2
[My-Documents]
        path = /home/Jonas/Desktop/My-Documents
        read only = no
;       browseable = yes
        guest ok = yes

The workgroup name is the same as the workgroup name on the Windows PC.

Firewall on Fedora linux pc is down.

I do get the following output when restarting smb :
Code:

apr 27 12:27:49 jonashp.domain.local systemd[1]: Starting Samba SMB Daemon...
apr 27 12:27:49 jonashp.domain.local smbd[4324]: [2015/04/27 12:27:49.686796,  0] ../source3/param/loadparm.c:3034(lp_set_enum_parm)
apr 27 12:27:49 jonashp.domain.local smbd[4324]: WARNING: Ignoring invalid value 'share' for parameter 'security'
apr 27 12:27:49 jonashp.domain.local smbd[4324]: [2015/04/27 12:27:49.687187,  0] ../source3/smbd/server.c:1286(main)
apr 27 12:27:49 jonashp.domain.local smbd[4324]: standard input is not a socket, assuming -D option
apr 27 12:27:49 jonashp.domain.local systemd[1]: Started Samba SMB Daemon.

I thought it would be that simple...

hi guys,

i know what initialization systems are, and pretty much what they do.
lately everybody has been giving out about various distros changing to systemd...

firstly have i got this right?

init is pretty much retired and used on many older distros

debian used init then switched to upstart and now uses systemd...though you can keep using upstart but its difficult to get right.

slackware uses a hybrid type sysv with bsd like scripting...

centos 7 is using systemd by default

so what is the big fuss? why would a poor init system steer people away from a distro they have used for years.

can it really be this important? i mean how many times a day are you going to reconfigure start-up services etc...i dont understand this.

Hello,

I try to use a ftp daemon and a Telnet daemon with inetd and the BusyBox v1.19.0 on a linux 2.6.24.

When running inetd and then checking what is listening with "netstat -an |grep LISTEN" i have :
Code:

netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN

tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN

tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN

ftp port 21 and Telnet port 23 seems to be listening.

My inetd.conf file is :

Code:

#<service_name>    <sock_type>    <proto>    <flags> <user>     <server_path>     <args> 

21 stream tcp nowait root ftpd ftpd /etc
telnet            stream        tcp        nowait    root    /usr/sbin/telnetd

I have no rule in my hosts.deny so nothing should be stopped and i have no iptables firewall in place too.

When typing "ftp://ipofthetarget" in a web browser i have a error :

Code:

504 Gateway Timeout
Gateway timeout expired while waiting for server response.

And when trying to Telnet from another computer or "Telnet localhost" from the board i have :
Code:

# telnet 10.2.29.201
Trying 10.2.29.201...
connected to 10.2.29.201.
Escape character is '^]'

Connection closed by foreign host.

This would mean that the connection for Telnet exist but why is it closing ?

Thank you for your future answers !

UPDATE 1 :
If i try to run telnetd like this :
/usb/sbin/telnet -l /bin/sh
i can connect anonymously from another computer, not perfect because i would like a user/password but still of use.
The problem with the ftp daemon still exist.

UPDATE 2 :
Trying from Windows cmd or linux terminal : ftp ipofthetarget seems to work
Not perfect because i would like a user/password too but still of use.

I am still open for suggestion for the user/password thing. I am not deleting the thread in case someone interested about this exist.

I have a dedicated PC providing storage of my music collection and streaming albums via Logitechmediaserver (LMS). OS is Arch running headless. For performance purposes I'd like LMS to access its SQLite database files from a RAM disk which must be dynamically created on startup of the PC with DB copied across from HDD prior to startup of LMS. On shutting down the PC the only changed files should be copied from the ramdisk back to the HDD. The intent would be to use rsync for the copying.

/etc/fstab is configured to create the ramdisk on startup:
Code:

tmpfs      /mnt/ramdisk tmpfs     defaults,size=4096M 0    0

and LMS has already been configured to look for its DB files in /mnt/ramdisk.

LMS' unit file is /usr/lib/systemd/system/logitechmediaserver.service. Its contents is as follows:
Code:

[Unit]
Description=Logitech Media Server Daemon
After=network.target

[Service]
User=logitechms
Group=logitechms
PIDFile=/var/run/lms.pid
WorkingDirectory=/opt/logitechmediaserver
ExecStart=/opt/logitechmediaserver/slimserver.pl \
	--prefsdir /opt/logitechmediaserver/prefs \
	--cachedir /opt/logitechmediaserver/cache \
	--logdir /opt/logitechmediaserver/Logs

[Install]
WantedBy=multi-user.target

On the startup leg, the data needs to be copied prior to launch of LMS, on the shutdown leg, LMS needs to be stopped and trigger the rsync diff copy. How would I best go about calling a script on startup and shutdown of the PC to ensure that the contents is synced to and from ramdisk on startup and shutdown?

Ok, here is what I've done so far, perhaps someone can critique it for me:

I created a file /etc/systemd/service/sync-lms-to-ramdisk.service containing the following:

Code:

[Unit]
Description=Copy LMS data data directory to ramdisk
After=network.target
Before=logitechmediaserver.service

[Service]
ExecStart=/usr/bin/sync-lms-to-ramdisk.sh

[Install]
WantedBy=multi-user.target

I then created /usr/bin/sync-lms-to-ramdisk.sh containing the following:
Code:

#! /bin/sh 
# /usr/bin/sync-lms-to-ramdisk.sh
#

rsync -av /mnt/md127/zSqueezeCache/ /mnt/ramdisk/
exit 0

I made it executable as follows:
Code:

chmod 755 /usr/bin/sync-lms-to-ramdisk.sh

I then enabled the Unit as follows:
Code:

systemctl enable sync-lms-to-ramdisk.service

If I'm not mistaken that should ensure that the ramdisk is populated before LMS fires up

Well, rebooted the server and the ramdisk is populated, but all is not well - LMS is inaccessible.

# systemctl status logitechmediaserver yields:

Code:

# systemctl status logitechmediaserver
● logitechmediaserver.service - Logitech Media Server Daemon
   Loaded: loaded (/usr/lib/systemd/system/logitechmediaserver.service; enabled)
   Active: inactive (dead) since Sun 2015-03-08 17:25:46 SAST; 18min ago
  Process: 411 ExecStart=/opt/logitechmediaserver/slimserver.pl --prefsdir /opt/logitechmediaserver/prefs --cachedir /opt/logitechmediaserver/cache --logdir /opt/logitechmediaserver/Logs (code=exited, status=0/SUCCESS)
 Main PID: 411 (code=exited, status=0/SUCCESS)

cat /usr/lib/systemd/system/logitechmediaserver.service yields:
Code:

[Unit]
Description=Logitech Media Server Daemon
After=network.target

[Service]
User=logitechms
Group=logitechms
PIDFile=/var/run/lms.pid
WorkingDirectory=/opt/logitechmediaserver
ExecStart=/opt/logitechmediaserver/slimserver.pl \
	--prefsdir /opt/logitechmediaserver/prefs \
	--cachedir /opt/logitechmediaserver/cache \
	--logdir /opt/logitechmediaserver/Logs

[Install]
WantedBy=multi-user.target

Quick question - is /etc/fstab processed before all of the abovementioned?

Ok, I've got the problem narrowed down to folder permissions. for some reason on creation of the ramdisk its owner is samba whereas it should be owned by logitechems. I amended /usr/bin/sync-lms-to-ramdisk.sh to change ownership of /mnt/ramdisk to logitechms:
Code:

 
#! /bin/sh 
# /usr/bin/sync-lms-to-ramdisk.sh
#

chown logitechms:logitechms /mnt/ramdisk/
rsync -av /mnt/md127/zSqueezeCache/ /mnt/ramdisk/
exit 0

However, on reboot ownership is again assigned to samba

Any ideas?

Hi experts,

so the steps to install kvm is this:

Code:

sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager

according to this webpage: http://www.howtogeek.com/117635/how-...nes-on-ubuntu/

Can I make this simpler?

I want to do just one command: sudo apt-get install kvm, and it should call and install all these packages.

Thanks

I am running two linux web-servers. One I am just setting up. On the other, I noted the following partition:
Code:

>df -h
Filesystem                      Size  Used Avail Use Mounted on
/dev/mapper/Machinename-root     27G  4.1G   21G  17 /
udev                            996M   12K  996M   1 /dev
tmpfs                           202M  792K  201M   1% /run
none                            5.0M     0  5.0M   0% /run/lock
none                           1006M  224K 1006M   1% /run/shm
/dev/sda1                       228M   90M  126M  42% /boot
/home/Amy/.Private               27G  4.1G   21G  17% /home/Amy

But on the one that I am installing, so far I get this:
Code:

>df -h
Filesystem              Size  Used Avail Use% Mounted on
udev                    996M   12K  996M   1% /dev
tmpfs                   202M  792K  201M   1% /run
none                    5.0M     0  5.0M   0% /run/lock
none                   1006M  224K 1006M   1% /run/shm
/dev/sda1               228M   90M  126M  42% /boot

How did I get /dev/mapper partition?

Hello,

I have CentOS 6.5 deployed as a VM on VMware ESXi. I want to force user to force password change even when they use VMware's vSphere client to access the VM console.

I tried the following two commands -

Code:

chage -d 0 username

Code:

passwd -e username

These commands force password change only when we start a SSH session for that user, not if that user access the VM directly via the client console. How do I achieve a force password change even when it is accessed via the client console?

Thanks

Bhushan Pathak

Hi. I am relatively new to linux systems. I recently jumped on an endeavor to install a vanilla kernel (3.18.5) from the kernel website. Its Documentation/Changes file mentions the minimum version requirements of the packages needed. For udev, it mentioned Code:

udevd --version

to check the version number. But looking around I found for Fedora its Code:

udevadm --version

(I'm using Fedora Workstation 21 64-bit). Is there any fundamental difference between these two utilities? Any explanation would be helpful.