SOLVED - Re: No startup of daemon at installation

2010-03-23 Thread Markus Meyer
Sjoerd Hardeman schrieb:
> Another option would be to download the deb, unpack it and manually edit
> the configuration scripts not to execute the init routine.
> I don't think there's an easier way. It's not apt that calls the init,
> it's the package its configuration scripts.
> Maybe somebody else has a clever idea.

Found it. In the "rules" file in the packages debian-directory I had to
change this:
# diff rules rules.orig~
92c92
<   dh_installinit --no-start
---
>   dh_installinit

Now the daemon won't start at installation time.

Hard to find that thing ;)

Cheers, Markus


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ba8bf97.6060...@koeln.de



Re: No startup of daemon at installation

2010-03-23 Thread Markus Meyer
Sjoerd Hardeman schrieb:
> So you don't want the daemon to be started straight away but it should
> start when you reboot? Why? What do you want to accomplish?

I don't want the service to start at installation time only. It seems
that as soon as there is a Init-script in the package, dpkg seems to
start the service.  So I'm looking for a way, to tell dpkg/apt/aptitude
not to start the daemon during installation.

As to why? The installation goes together with a firmware upgrade of a
RAID-controller and this needs a reboot afterwards. And the daemon must
not start only to be shut down again after a few seconds when I reboot
the server.

> Note that you can always stop a daemon by running
> /etc/init.d/servicename stop.

I know, thanks.

Cheers, Markus


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ba8b818.2050...@koeln.de



No startup of daemon at installation

2010-03-23 Thread Markus Meyer
Hi all,

I'm building a server package for myself and I don't want it to start at
installation. I could use an /etc/default/servicename file with
something like START_SERVICE=no. But I want this service to start at
boot time. So I'm forced to edit the default file after the
installation. Is there another way?

Thanks for any suggestions,

Markus


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ba88b54.3060...@koeln.de



Re: Mount of ext3 Partition on other hardrive does not work

2004-07-10 Thread Markus Meyer
Silvan wrote:
> How about mounting the partitions in question as ext2 temporarily until
> you can work out what's going wrong?  

Nice try, but mount spits out the same error like before.

Cheers,

Markus


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Mount of ext3 Partition on other hardrive does not work

2004-07-10 Thread Markus Meyer
Hi folks,

I seem to have a little isue here. My linux system is completely on 'hda'
and I have two other disks (hdb & hde) attached to my PC, where 'hde' is
attached via a Promise Ultra100 TX2 adapter. 
'hdb' looks like that:
# fdisk -l /dev/hdb
Disk /dev/hdb: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/hdb1   *   1   7657638594272+  83  Linux
/dev/hdb2   76577   77545  488376   82  Linux swap

and 'hde' like that:
# fdisk -l /dev/hde
Disk /dev/hde: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/hde1   1   7754539082648+  83  Linux

Both have a ext3 FS on it. It has been created with 'mke2fs -j -c /dev/hde1'
And I can't mount any of the partitions, swap excepted ;) But using Knoppix
3.4 with a 2.4.26 Kernel, I was able to mount all of the above partitions.
Also I tried it with the PLD-Linux Rescue Disk, which has a 2.6 Kernel, it
didn't wotk again. Oh, I had this also with 2.6.5 & 2.6.6. I have no idea
what's wrong there, except it's a bug in 2.6.  Any ideas or suggestions are
_very_ welcome. I nearly despair.

Cheers,

Markus


Here some more info:

Kernel: 2.6.7 on Debian Unstable with ext3 comiled in

3 fsck /dev/hdb1
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
/: clean, 140976/4833280 files, 824782/9648568 blocks

Fsck tells me the same for /dev/hde1.

# mount -t ext3 /dev/hdb1 /mnt
mount: /dev/hdb1 already mounted or /mnt busy
#ÂÂmountÂ|ÂegrepÂ'(mnt|hdb)'
#ÂÂfuserÂ/mnt
# ls -al /mnt
total 8
drwxr-xr-x2 root root 4096 Jun  6 18:56 .
drwxr-xr-x   30 root root 4096 Jul  6 21:04 ..
# mount
/dev/ide/host0/bus0/target0/lun0/part1 on / type unknown
(rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw,devmode=0666)
/dev/mapper/vg1-scratch on /scratch type ext3 (rw,noexec,nosuid,nodev)
/dev/mapper/vg1-home on /home type ext3 (rw)
/dev/mapper/vg0-usr on /usr type ext3 (rw)
/dev/mapper/vg0-var on /var type ext3 (rw)
/dev/mapper/vg0-opt on /opt type ext3 (rw)
/dev/mapper/vg1-team on /team type ext3 (rw,noexec,nosuid,nodev)
automount(pid2225) on /media type autofs
(rw,fd=5,pgrp=2225,minproto=2,maxproto=4)
# cat /etc/fstab
# /etc/fstab: filesystem table.
#
#   
/dev/hda1/ext3defaults,errors=remount-roÂÂ0ÂÂÂ1
/dev/hda2noneswapswÂÂÂ0ÂÂ0
procÂ/procÂÂÂprocdefaultsÂ0ÂÂÂ0
sysfs/syssysfsÂÂÂdefaultsÂÂ0ÂÂÂ0
none/proc/bus/usbÂÂÂusbfsÂÂÂdefaults,devmode=0666ÂÂÂ0ÂÂ0
/dev/fd0ÂÂÂ/floppyÂvfatÂÂÂ
ÂÂÂdefaults,user,noauto,showexec,umask=022Â0ÂÂÂ0
/dev/cdromÂÂ/cdromÂautodefaults,ro,user,noexec,noautoÂÂ0ÂÂÂ0
/dev/cdrwÂÂÂ/cdrwÂÂautodefaults,ro,user,noexec,noautoÂÂ0ÂÂÂ0
/dev/vg1/scratch/scratchÂÂÂext3defaults,noexec,nosuid,nodev0ÂÂÂ2
/dev/vg1/homeÂÂÂ/homeÂÂÂext3defaultsÂÂÂ0ÂÂÂ2
/dev/vg0/usr/usrÂext3defaultsÂÂ0ÂÂÂ2
/dev/vg0/var/varÂext3defaultsÂÂ0ÂÂÂ2
/dev/vg0/opt/optÂÂext3defaultsÂ0ÂÂÂ2
/dev/vg1/teamÂÂÂ/teamÂÂext3defaults,nosuid,noexec,nodev0ÂÂÂ2
# lspci
:00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333]
:00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333 AGP]
:00:09.0 Unknown mass storage controller: Promise Technology, Inc.
PDC20268 (Ultra100 TX2) (rev 02)
:00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1
(rev 07)
:00:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
(rev 07)
:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
:00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
:00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 23)
:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP
(rev 03)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



SOLVED: Re: Exim4 error - group mail not found

2004-07-10 Thread Markus Meyer
Markus Meyer wrote:

> Line 266 only says group = mail. But the group mail does exist my system
> (/etc/group: mail:x:8:) and the mail-dir also has the correct perms:

After I changed the 'mail' entry to it's numeric GID '8' it worked again.
Really weird.

Bye,

Markus


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: 2.4.X to 2.6.X pb

2004-07-10 Thread Markus Meyer
Yohann Desquerre wrote:

> Hi all,

Hi alone, 

> 
> VFS : unable to mount root fs on unknown-block(0,0)

Have you compiled in your filesystem driver? If you have ext3 you need ext3
not as module, but compiled into the kernel?

Cheers, 

Markus


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Exim4 error - group mail not found

2004-07-10 Thread Markus Meyer
Hi folks,

since two days my Exim4 won't start allthough I can't remember making any
changes to it's config. It's running as relay to forward my mails I write
with Mutt to my Mail-Provider. My system is a Debian-Unstable. When I start
Exim the folowing comes out:
Starting MTA: 2004-07-10 09:56:25 Exim configuration error in line 266
of /var/lib/exim4/config.autogenerated.tmp:
ÂÂgroupÂmailÂwasÂnotÂfound
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp
not installing /var/lib/exim4/config.autogenerated.tmp to 
/var/lib/exim4/config.autogenerated

Line 266 only says group = mail. But the group mail does exist my system
(/etc/group: mail:x:8:) and the mail-dir also has the correct perms:
[butterblume 16] apt > la /var/mail
insgesamt 32
drwxrwsr-x7 root mail 4096 2004-07-10 14:09 .
drwxr-xr-x   18 root root 4096 2004-03-26 22:30 ..
-rw-r--r--1 root mail0 2003-08-08 20:32 .dead_bounces
drwx--2 root mail 4096 2003-08-08 20:20 error
-rw---1 fetchmail mail0 2004-07-10
09:50 .fetchmail-UIDL-cache
drwxr-sr-x2 root mail 4096 2003-08-08 20:36 input
-rw-r--r--1 mail mail0 2003-08-08 20:36 .lasttimedone
drwxr-sr-x2 root mail 4096 2004-07-10 09:47 mail
-rw-r-1 markus   mail0 2004-02-27 17:32 markus
drwxr-sr-x2 root mail 4096 2003-08-08 20:36 msglog
-rw-rw1 root mail  966 2003-07-29 17:05 root
-rw-r--r--1 root mail0 2003-08-08
20:32 .tempfail_bounces
-rw-r--r--1 root mail0 2003-08-08 20:32 .thistime
drwxrwx---2 root mail 4096 2003-08-08 20:36 tmp


Any ideas or suggestions are welcome ;)


Cheers,

Markus


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]