I have installed SystemD in in parallel to SysVInti(with OpenSUSE enhancements). When I starting SystemD, startpar is also running. I suppose, i should add starpar.unit to SystemD configuration. I asks for help, because I won't broke my system.
View 2 RepliesWhat is the correct/safe way to move from upstart to systemd? I originally installed upstart in 11.3 and have now upgraded to 11.4. Having successfully upgraded to 11.4 I tried to use yast2 to install systemd and systemd-sysvinit onto my running system. Yast correctly identified that upstart should be deinstalled as a prerequisite for installing systemd-sysvinit.
After the install of systemd the system wouldn't shut down, and on a reset the system reported many systemctl/start service timeouts on things such as mounts and ttys. Eventually the system started an X-windows KDM login, but there were no console ttys and mounts were missing. I used X/kdm to login to root - phew! - I restored / from an rsync backup I'd made prior to the changes, so I'm back in business with upstart. I'd like to tidy up and move to systemd - I going to have a nose around myself, perhaps I will try switching back to sysv init and then going to systemd - but I have to wait for the machine to be idle before I experiment, any info in the mean time would be great.
I'm looking to install an nVIDIA driver (sh NVIDIA-Linux-x86_64-190.53-pkg2.run is the command I used) but it tells me I need to do it when the xfree isn't running
So what I'm looking for is a way to boot up to the command line, is that possible on SUSE 11.2?
For a number of openSUSE releases now, on a periodic basis (monthly, it seems?) both my laptop and my desktop take forever to start. During this time, the hard disk activity is going berserk. When inspecting this with "iotop", a process called "preload" or "start_preload" is hammering the disk, sometimes up to 10 minutes.
The irony is when you research "preload", you find mostly articles like "drastically speed up your Linux system with preload"- I sometimes think it has to do with running VMs on these machines and maybe it's trying to cache those large disk images? Pure speculation, but I can't seem to find any documentation on this.
Anyway, I did finally find a way to turn this thing off. WARNING: since I do not know exactly what preload does and whether your machine becomes unusable if you turn it off, please only follow these instructions at your own risk. Since preload seems to be a very low-level system/service, I did not want to risk uninstalling it. What I did instead was:
Yast2 - System Services (RunLevel)
Click the Expert Mode radio button
Scroll down to the boot.startpreload entry
[code].....
Since I applied these steps, no long boot times with insane hard disk activity has occurred and I also have not noticed anything else complaining or not working with this service off.
I've proven that the the D in systemD is for DISASTER.At first, I thought that the dozens of problems I had with startup, shutdown, and services, was due to my upgrading from Fedora 14. But now that I've tried a fresh install, I have a new set of different problems. Basically DBUS broke after I installed Samba, and no combo of reinstalling either of them fixed anything. So here goes my third Fedora 15 install.
During a fresh install, can I de-select systemd and select upstart and sysv instead? systemd is not visible in the GUI installer. Do I need some Kickstart hack or something? Is this possible at all?
I can disable the internet in mswin(XP) to gain some FPS in games. How can I disable the internet and enable the internet as needed? I have suse 11.4 and kde. Through command line?
View 9 Replies View RelatedI wanna disable the vertical scroll of the track on my aspire one,... Before I did this with Sax2, but now, there is no sax, so??
View 1 Replies View RelatedI've set up a media box for mythtv based on OpenSUSE 11.3 and LXDE. By default, the screen gets locked prior to a suspend. On resume, therefore, the screen is locked and requires a password to unlock. I need to disable this action. In KDE4, I can do that by going to the power management settings and un-selecting the appropriate check box. In LXDE, however, I can find no such settings. There must be a config file somewhere that I can tweak to turn off the screen lock prior to suspend, but I have no idea what it is.
View 5 Replies View RelatedI've had a hell of a time with this and now all but YAST2 are ok. Going back some time to 10.0 this could be used to disable it very completely.
open terminal and run
echo "alias net-pf-10 off" >> /etc/modprobe.conf
echo "alias ipv6 off" >> /etc/modprobe.conf
restart computer. Has anyone used this on more recent issues even 11.4 and are there any repercussions?I assume that the inverse will but it back on ie off's just become on's? I will be using cups when I install my printer which is one concern and I am not at all sure that modprobe will do anything anymore?
I also recollect that there is a command to cause the kernel to effectively reboot which would save restarting. Can't remember what it is. Maybe some one can refresh my memory.
For reasons long and unique, I want to disable UUID in my recent Ubuntu 10.4 install, and use the old fashioned /dev/sda1 /dev/sdb3 etc. method. I had this "all fixed" under GRUB (pre-2) on Ubuntu 8.04 and it has served well and bug free for years. (Warning: I use old stable hardware - others may have disasters.) But with GRUB2, the task seems more complicated. (This guide me make the backups I haven't done since the fresh install 2 weeks ago.)
Is the following process complete, necessary, and accurate...
Edit the file /etc/default/grub to remove the # in the line...
#GRUB_DISABLE_LINUX_UUID="true"
... making sure to add the two " if missing .....
Copy nearly the entire /boot/grub/grub.cfg file
into /etc/grub.d/40_custom and then...
Comment out every line that says...
search --no-floppy --fs-uuid --set (etc.)
Change every line that says...
linux /boot/vmlinuz-2.x.yy-zz-generic root=UUID=(etc.) into...
linux /boot/vmlinuz-2.x.yy-zz-generic root=/dev/sda1
Edit /etc/fstab and change every instance of UUID=(etc.)
to the appropriate drive and partition e.g. /dev/sda1
edit /etc/initramfs-tools/conf.d/resume and change RESUME=UUID=(etc.)
into RESUME=/dev/sda1
Run update-grub
Do all the above, every time I do a kernel upgrade. (Is it important to do all the above before or after rebooting for an upgrade?) Am I correct, succinct, and complete in the above process? Any mistakes? Any omissions?
Since I have upgraded to KDE 4.5 I can't play games (native or wine) without disabling composite before start playing.When I start a game its window begins to shiver (to tremble or to shake... not sure) and so I have to disable composite first and then relaunch the game.I never had to do this in KDE 4.4.
View 2 Replies View RelatedI am a brand new user coming from the MS environment. My impression of openSUSE is that it is like moving into a new house that is well built but the rooms are full of half-constructed self-assembly furniture and appliances without any specific instructions. Nor is it clear which does what and whether all are needed or not. There is a town hall down the road where fellow homeowners gather to discuss what each has managed to deduce about putting their own furniture together. The town hall has a sort of library where thousands of pieces of paper with instructions are stored in an ad-hoc filing system
My latest problem is that I have created a screensaver via the "Configure Desktop" application and set "Enable display power management" and set some timeouts.However, I seem to be asked for a password to unlock the screen when I come back to my computer. I have spent 2 hours trying to find the place where I can disable screen password locking but to no avail. I am perplexed and frustrated at how such an obvious function is so ****ed hard to configure. This is the impression I am getting of Linux in general - it is novice user-hostile and badly organised.
I'm using Gnome on openSUSE 11.2. I can't get rid of the ctrl-alt-d keyboard shortcut in Gnome. I have set it to "disabled" in control center -> keyboard shortcuts, but no luck.
When I run the gnome-keybindings-properties program from the terminal it dumps these two messages onto stderr:
(gnome-keybinding-properties:11958): keybinding-properties-WARNING **: No description for key '/apps/compiz/general/allscreens/options/opacity_decrease_key'
(gnome-keybinding-properties:11958): keybinding-properties-WARNING **: No description for key '/apps/compiz/general/allscreens/options/opacity_increase_key'
and the following two messages like 20 or so times:
(gnome-keybinding-properties:11958): Gtk-CRITICAL **: gtk_tree_store_append: assertion `VALID_ITER (parent, tree_store)' failed
(gnome-keybinding-properties:11958): Gtk-CRITICAL **: gtk_tree_store_set_valist: assertion `VALID_ITER (iter, tree_store)' failed
I realize this isn't the most critical problem, but I am experimenting with Guile (scheme as a C extension language) which I am editing in Emacs, and even after reassigning "down-list" I keep hitting C-M-d because it's right by C-M-f which I also use constantly, and this minimizes all my windows! And there is nothing on my desktop, I never use the feature intentionally. Maybe I should get a wallpaper that says "HaHa Dummy!" or something of the sort to at least get a chuckle out of it when it happens.
Because of my problem here:[URL]..I'd like to replace upstart with systemd on F14. Is this as simple as a yum install? In the wiki is it's referred to as a "technology preview" for F14, which is meaningless to me; there are no further notes about installing or enabling it.
View 1 Replies View RelatedI've bought an Acer Aspire 5810T(imeline),I notice after installation of opensuse 11.2 that network-manager has been installed by default probably because my laptop computer is containing a wireless device.I only want my computer using ethernet (with the cable) and so want to know which methods exist to shut down as securely as possible wireless to avoid any missuse activity
Is there any possibility to shutdown traffic by locking with a password?I do not have any wifi relay or antenna at home but want to avoid any relay in my neighbourhood from getting into my computer.
I leave my system in suspend mode overnight and wake it up first thing in the morning. At 9:15 it will automatically run housekeeping scripts via cron and these are completed by 9:30. Some time later I will turn on the monitor and start work. Since moving from Wheezy to Jessie the system has switched off for no apparent reason. I checked the syslog and auth.log and found it completed all it's tasks at 9:30 then started shutting down at 9:35. Relevant extracts from these logs are attached ...
My OS is Jessie 64 bit with Cinnamon on a quite standard Gigabyte desktop with dual core intel processor, 4Gb RAM and SSD drive. It uses NVidia drivers and there were no unusual entries in x.org.log.
AUTH LOG
May 21 09:36:15 michael systemd-logind[685]: System is powering down.
May 21 09:36:15 michael gnome-keyring-daemon[1477]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
May 21 09:36:15 michael lightdm: pam_unix(lightdm:session): session closed for user michael
May 21 09:36:16 michael polkitd(authority=local): Unregistered Authentication Agent for unix-session:1 (system bus name :1.39, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_AU.UTF-8) (disconnected from bus)
May 21 09:36:16 michael sshd[680]: Received signal 15; terminating.
[Code] .....
I was trying to install recent updates, but apt-get couldn't do this. Here's the output I got:
Code: Select all(Reading database ... 187979 files and directories currently installed.)
Preparing to unpack .../udev_215-17+deb8u1_i386.deb ...
Failed to execute operation: Connection reset by peer
Message from syslogd@debian-LAPTOP at Jun 6 14:56:49 ...
kernel:[357720.299647] systemd[1]: segfault at b87cf92c ip b765e480 sp bf872e60 error 4 in systemd[b762f000+130000]
Unpacking udev (215-17+deb8u1) over (215-17) ...
Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
[Code] ....
Now I can't continue upgrading because every time it tries to finish the previous update and fails to process udev.
I don't know if it's relevant, but while upgrading udev for the first time, my laptop switched to tty1 on its own. When I switched it back to graphic subsystem, it still was in process of upgrading udev or systemd and after all failed to finish.
When i login on localhost with pubkey-auth, i get the following in my log
Code: Select allSep 20 12:42:27 aldebaran sshd[19745]: Accepted publickey for root from 127.0.0.1 port 37520 ssh2: RSA 45:4e:27:4d:30:f5:3d:25:10:d0:92:88:53:77:1a:3b
Sep 20 12:42:27 aldebaran sshd[19745]: pam_unix(sshd:session): session opened for user root by (uid=0)
Sep 20 12:42:27 aldebaran systemd[19757]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Sep 20 12:42:27 aldebaran systemd-logind[585]: New session 70 of user root.
Sep 20 12:42:27 aldebaran systemd[19757]: Starting Paths.
[code]....
When I boot my debian desktop, I get these errors:
Code: Select allnov 08 22:05:12 Luca-PC systemd[1]: Job paths.target/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:12 Luca-PC systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:15 Luca-PC systemd[1]: Job paths.target/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:15 Luca-PC systemd[1]: Job sysinit.target/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:15 Luca-PC systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with sysinit.target/start
The system works perfectly, but I'd like to understand why I get these errors, and how I can fix them.
How to log "remaining processes"? How to know their names?
Code: Select allsystemd-shutdown[1]: Sending SIGTERM to remaining processes...
During the boot-sequence of jessie there is more text flying by on the screen (including some errors or warnings) than I can read thorugh fast enough. I don't think this is very serious stuff, and if it were I could always look at dmesg and or syslog i /var/log but I would find it really convenient to log these messages in a file instead of sifting through or grep-ing dmesg.
When duckduckgoing this matter I found [URL] ....
I installed tried bootlogd but when configuring it to "yes" and rebooting nothing comes up in /var/log/boot.
Then I saw this line in above link
If you use systemd as your init system, you may need to use systemctl to debug boot problems.
I tried to set up my linux server with a specific script that can control my gameserver (mta). The thing is, I wanted to let this script be forced to start by the systemd, so I created a service called 'mtadef' (btw: same name as the user).
Here is the service script:
Code: Select all[Unit]
Description="MTA: Primary Server"
[Service]
Type=Forking
User=mtadef
ExecStart=/home/mtadef/mtastart.sh
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
And here is my shellscript (mtastart.sh):
Code: Select all#!/bin/sh
if [ $# -ne 1 ]
then
screen -S MTA_def /home/mtadef/mta-server64 -screen 0 800x600x16 -ac
exit 1
[Code] ....
When I try to start the service by the command "systemctl start mtadef" now, I returns me the message:
"Must be connected to a terminal."
On macbook air 6.2, i've installed a Debian jessie mate DE, dual boot using refind. I'm currently fine-tuning it. I've made a script following powertop advice:
Code: Select all[newb@debian /etc/systemd/system]$ cat mba_kb_sp.sh
#!/bin/sh
echo 'auto' > '/sys/bus/usb/devices/1-3.1/power/control';
echo 'auto' > '/sys/bus/usb/devices/1-3.2/power/control';
echo 'auto' > '/sys/bus/usb/devices/1-5/power/control';
exit 0
[Code] ....
All seems to work fine, however when i check the sys file it didn't change. But I can start manually the systemd service and, this time, it works.
I upgraded my machine from Wheezy to Jessie, opted to not install systemd yet. When i try to upgrade kde-plasma-desktop, apt doesn't let me do it.
For some reason "libpam-systemd : Depends: systemd (= 215-17+deb8u1) but it is not installable"
Installing systemd-shim doesn't work. Libpam-systemd package site gives impression that you would be able to use systemd or systemd-shim.
Tried looking through changelog, but it didn't really give any hint.
At 215-6 there are just
Code: Select allSwitch libpam-systemd dependencies to prefer systemd-shim over
systemd-sysv, to implement the CTTE decision #746578. This is a no-op on
systems which already have systemd-sysv installed, but will prevent
installing that on upgrades. (Closes: #769747)
Version of libpam-systemd that would be installed is "Candidate: 215-17+deb8u1"
When I first started running Jessie 8.1 I noticed that after the disk check the boot was quiet, ie. no messages to the terminal . However, something has happened and now when I boot the machine I get a verbose listing of all the processes being started. Is there a way to change it back to the way it was? In other words a quiet boot. The only thing I know of that has been 'anomalous' behavior is the other day when doing a mp4 to avi conversion, using avconv, I apparently had an over temp condition which closed my LXDE session and brought me to the login prompt. Don't know what other info one may need but feel free to ask for more, if necessary.
View 13 Replies View Relatedmy system keeps on telling me about an error:
Code: Select allsudo journalctl -p 0..3
Apr 14 10:36:11 debian ntpd_intres[682]: host name not found: ptbtime1.ptb.de
Apr 14 10:36:11 debian ntpd_intres[682]: host name not found: ptbtime2.ptb.de
Apr 14 10:36:11 debian ntpd_intres[682]: host name not found: ptbtime3.ptb.de
A quick check
Code: Select allsystemctl status ntp.service
ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp)
[code]...
3 packets transmitted, 0 received, 100% packet loss, time 1999ms.Same result when using the standard Debian ntp time servers like "server 0.debian.pool.ntp.org iburst" in /etc/ntp.conf.
We have seen with the release of Fedora 15, systemd is the new start-up services, which will replace SysVinit and Upstart on most Linux distributions. Here are some tips based on the order systemd-analyze, for analyzing the startup time of your OS.On commence avec l'option time, qui affiche le temps total de d�marrage de votre syst�me : (One starts with l' option time, which posts the total time of starting of your system: )
Code:
$ systemd-analyze time
Startup finished in 6385ms (kernel) + 3228ms (initrd) + 49335ms (userspace) = 58949ms
[code]....
I've just upgraded to Fedora 15 and have been fiddling with the new systemd which replaces sysvinit. I googled quite a bit, but was really unable to find any real information about how it works and why it's better.
View 1 Replies View RelatedHow to enable persistent logging with systemd? I find it really weird that all this machinery that is systemd doesn't store persistent logs, what if I'm trying to retrieve some information regarding previous boots?
For instance: I have random suspend issues, after rebooting the computer there's no trace left in the logs of what happened, and furthermore (at least in Jessie) I can no longer see a pm-suspend log.
So, at first it sounds like all you have to do is edit journald.conf setting #Storage=auto to "persistent" and create the /var/log/journal directory, but then reading here /usr/share/doc/systemd/README.Debian
Code: Select allEnabling persistent logging in journald
=======================================
To enable persistent logging, create /var/log/journal and set up proper permissions:
install -d -g systemd-journal /var/log/journal
setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal
and here [URL] ....
There are two main reasons why I decided to not enable persistent logging just yet ....
We did get corrupt journal files in the past where the journal then no longer worked at all [1]. With volatile you can just reboot and have a clean state again. Admittedly, the journal has seen a lot of improvements in the mean time and hopefully is more robust, so this point is no longer true.
We still install rsyslog by default. That means we get store them twice. This is something we don't want to do atm.
I have SSD drives without SCT support, because of this I want to tune /sys/block/device-name/device/timeout in order to force mdadm put these drives offline. So, I can see my drive like this:
/dev/disk/by-id/ata-OCZ-SABER1000_A22MJ061512000074.
Where can I tune /sys/block/device-name/device/timeout from 30 to 7 sec only for these drive? I don't want to use rc.local.
Can I create right udev rules for it in /etc/udev/rules.d?
I want to avoid any conflict with /lib/udev/rules.d.
Code: Select all# udevadm monitor --environment --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UDEV [9302.549485] add /devices/pci0000:00/0000:00:01.2/0000:03:00.0/host0/target0:0:0 (scsi)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:03:00.0/host0/target0:0:0
DEVTYPE=scsi_target
SEQNUM=5210
SUBSYSTEM=scsi
[Code] ....