Mailinglist Archive: opensuse-bugs (4667 mails)

< Previous Next >
[Bug 639393] New: startpar fails for no apparent reason
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 14 Sep 2010 22:45:08 +0000
  • Message-id: <bug-639393-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

https://bugzilla.novell.com/show_bug.cgi?id=639393

https://bugzilla.novell.com/show_bug.cgi?id=639393#c0


Summary: startpar fails for no apparent reason
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: Other
OS/Version: openSUSE 11.3
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: rob.fortune@xxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.7
SUSE/7.0.513.0 (KHTML, like Gecko) Chrome/7.0.513.0 Safari/534.7

I have an openvz based VPS. Anyway, I deleted their distro and put OpenSUSE on
it of course. The init scripts fail for two reasons, but I will report only one
of them here.


Reproducible: Always

Steps to Reproduce:
1. Get a openvz container with suse in it
2. Boot it
3.
Actual Results:
Fails to boot with

tcgetattr: Inappropriate ioctl for device



Expected Results:
Completed boot

I checked out startpar from obs:

osc co 'openSUSE:11.3:Update' sysvinit


--- startpar.c~ 2009-08-20 12:11:03.000000000 +0100
+++ startpar.c 2010-09-14 23:31:28.541357764 +0100
@@ -893,7 +893,7 @@
if (tcgetattr(0, &tio))
{
perror("tcgetattr");
- exit(1);
+ //exit(1);
}
if (ioctl(0, TIOCGWINSZ, &wz) == 0)
wzok = 1;

Commenting out the exit line if that fails seems to have no effect and makes
OpenSUSE sysvinit scripts work in the openvz containers, with one other change
I will make a separate bug report for.

It does spew other errors about those tc* kernel interfaces but again they're
just spam and seem to have no effect, the system runs fine.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >