Re: [systemd-devel] Completion of error handling
On Sat, Jul 25, 2015 at 8:11 AM, SF Markus Elfring elfr...@users.sourceforge.net wrote: We accept contributions only in git-format-patch frmatted patches, best via github PRs. The higher level patch formats I'm trying to make you aware of will also result in file changes which can be integrated by this content management interface depending on your general acceptance for corresponding software evolution. Examples: * Scripts in the semantic patch language can be processed for occasional patch generation by the Coccinelle software. http://coccinelle.lip6.fr/papers.php * Aspect files could be transformed during an enhanced build process by the AspectC++ software. http://aspectc.org/Publications.php Would you like to give thoughts for the extension of the software development toolbox a chance? I am sorry, your questions are not useful, because too generic. I hope that the software situation can also be improved by development methodology and technology you are more familiar with at the moment. Would you like to reopen a specific bug report for example? No, systemd does not plan to do anything here. https://github.com/systemd/systemd/issues/644 Update candidates: * How do you think about to look at calls for functions from the application programming interface POSIX threads again? * Does the usage of file output functions need another look? No, nothing needs more discussion or attention in the context of systemd. None of the above seems contain anything useful or is expected to contribute anything useful in the future. This is a development mailing list, we discuss patches and actual code, and not vague questions like you ask. Please stop posting this stuff or asking any more questions like this. Thanks, Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Clarification around a segmentation fault from an udevd worker
On Sat, Jul 25, 2015 at 6:11 PM, SF Markus Elfring elfr...@users.sourceforge.net wrote: Hello, I would like to clarify the setting of device file permissions for my needs. So I extended the debug output at some source code places to see also better which lines are executed during my tests. I built these extensions for calls of the function log_debug on the current source files (last commit: 3460810e8c61986a4605ad80c9e4805eb95cb5a1) with the software GCC 5.2.0 on my openSUSE Tumbleweed system. I am experimenting a bit with this fresh server program. Sonne:~ # systemctl stop systemd-udevd.service systemd-udevd-kernel.socket systemd-udevd-control.socket /home/elfring/Projekte/Bau/systemd/systemd-udevd --debug Now I wonder about an error message like the following. … adding watch on '/dev/dm-0' … seq 2633 forked new worker [19879] seq 2633 running IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/40-libgphoto2.rules:9 unable to access usb_interface device of '/sys/devices/pci:00/:00:02.0/usb3/3-2/3-2:1.0' IMPORT builtin 'usb_id' returned non-zero IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11 worker [19879] terminated by signal 11 (Segmentation fault) worker [19879] failed while handling '/devices/pci:00/:00:02.0/usb3/3-2/3-2:1.0' … I would appreciate your advices. Can you try to run it under gdb? $ gdb /home/elfring/Projekte/Bau/systemd/systemd-udev Type r at the prompt to run it. if it shows the same error here as when it runs without gdb, type bt full at the prompt It should print the backtrace with the location where the error happened. Please paste that output into an email. Thanks, Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Completion of error handling
We accept contributions only in git-format-patch frmatted patches, best via github PRs. The higher level patch formats I'm trying to make you aware of will also result in file changes which can be integrated by this content management interface depending on your general acceptance for corresponding software evolution. Examples: * Scripts in the semantic patch language can be processed for occasional patch generation by the Coccinelle software. http://coccinelle.lip6.fr/papers.php * Aspect files could be transformed during an enhanced build process by the AspectC++ software. http://aspectc.org/Publications.php Would you like to give thoughts for the extension of the software development toolbox a chance? I am sorry, your questions are not useful, because too generic. I hope that the software situation can also be improved by development methodology and technology you are more familiar with at the moment. Would you like to reopen a specific bug report for example? https://github.com/systemd/systemd/issues/644 Update candidates: * How do you think about to look at calls for functions from the application programming interface POSIX threads again? * Does the usage of file output functions need another look? Regards, Markus ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] udev and dm inotify problems
Hi list. I ran into the strange problem. After creating encrypted swap (with crypttab) boot hangs. That happens because systemd waits for dev-mapper-swap.device. Udev doesn't report that this device active, because SYSTEMD_READY environment set to 0. That happens because change event was not generated. Change event was not generated, because udev doesn't receive inotify event after mkswap closes device. I come to this after verifying manually these steps: 1. Set udev log_level to debug 2. Attach device with systemd-cryptsetup 3. Verify that inotify for device was added (no errors in debug log, device in /run/udev/watch). Also I attach strace to systemd-udev. 4. Run mkswap /dev/mapper/swap 5. Check, that there was no any activity by systemd-udev (according to strace - no event, according to the logs - no processing) After figuring out this, I double check systemd requirements with /README.txt I'm running linux-4.1.3, systemd (c11ae0bacee4ab835526a7408f619a754b3b848e) Also I have this in config CONFIG_FHANDLE=y CONFIG_CGROUPS=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_CHECKPOINT_RESTORE=y CONFIG_NET_NS=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_SECCOMP_FILTER=y CONFIG_BLK_DEV_BSG=y CONFIG_EFI_PARTITION=y CONFIG_SECCOMP=y CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y CONFIG_DMIID=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_XFS_POSIX_ACL=y CONFIG_BTRFS_FS_POSIX_ACL=y CONFIG_F2FS_FS_POSIX_ACL=y CONFIG_FS_POSIX_ACL=y CONFIG_INOTIFY_USER=y CONFIG_AUTOFS4_FS=m CONFIG_PROC_FS=y CONFIG_SYSFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y CONFIG_EFIVAR_FS=m CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y I use next workaround: cat /etc/systemd/system/systemd-cryptsetup@swap.service.d/override.conf [Service] ExecStartPost=/usr/bin/udevadm trigger -t devices -p SYSTEMD_READY=0 So.. What I should check to make all that run properly? // wbr // Oleksii Shevchuk ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] udev and dm inotify problems
В Sat, 25 Jul 2015 09:51:25 +0300 Oleksii Shevchuk alx...@gmail.com пишет: Hi list. I ran into the strange problem. After creating encrypted swap (with crypttab) boot hangs. That happens because systemd waits for dev-mapper-swap.device. Udev doesn't report that this device active, because SYSTEMD_READY environment set to 0. That happens because change event was not generated. Change event was not generated, because udev doesn't receive inotify event after mkswap closes device. I come to this after verifying manually these steps: 1. Set udev log_level to debug 2. Attach device with systemd-cryptsetup 3. Verify that inotify for device was added (no errors in debug log, device in /run/udev/watch). Also I attach strace to systemd-udev. 4. Run mkswap /dev/mapper/swap 5. Check, that there was no any activity by systemd-udev (according to strace - no event, according to the logs - no processing) Could you verify with e.g. inotifywatch whether inotify event was generated by kernel? After figuring out this, I double check systemd requirements with /README.txt I'm running linux-4.1.3, systemd (c11ae0bacee4ab835526a7408f619a754b3b848e) Also I have this in config CONFIG_FHANDLE=y CONFIG_CGROUPS=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_CHECKPOINT_RESTORE=y CONFIG_NET_NS=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_SECCOMP_FILTER=y CONFIG_BLK_DEV_BSG=y CONFIG_EFI_PARTITION=y CONFIG_SECCOMP=y CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y CONFIG_DMIID=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_XFS_POSIX_ACL=y CONFIG_BTRFS_FS_POSIX_ACL=y CONFIG_F2FS_FS_POSIX_ACL=y CONFIG_FS_POSIX_ACL=y CONFIG_INOTIFY_USER=y CONFIG_AUTOFS4_FS=m CONFIG_PROC_FS=y CONFIG_SYSFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y CONFIG_EFIVAR_FS=m CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y I use next workaround: cat /etc/systemd/system/systemd-cryptsetup@swap.service.d/override.conf [Service] ExecStartPost=/usr/bin/udevadm trigger -t devices -p SYSTEMD_READY=0 So.. What I should check to make all that run properly? // wbr // Oleksii Shevchuk ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fstab generator and nfs-client.target
В Sat, 25 Jul 2015 12:50:39 +0200 Michael Biebl mbi...@gmail.com пишет: 2015-07-25 3:18 GMT+02:00 Rich Freeman r-syst...@thefreemanclan.net: I noticed that mount units for nfs shares created by the generator do not Want=nfs-client.target or similar. That means that if you don't explicitly want nfs-client in your configuration then nfs shares will get mounted, but services like rpc-statd-notify.service won't run. Would it make sense to have the generator add the nfs-client target as a want to nfs mount services it creates? remote mount units do have a After remote-fs-pre.target ordering and tools like nfs-common/rpcbind are supposed to hook up into remote-fs-pre.target. They are supposed to be /ordered before/ remote-fs-pre.target; but I do not remember that remote-fs-pre.target itself was intended to pull anything. This was designed as pure synchronization point. http://www.freedesktop.org/software/systemd/man/systemd.special.html#remote-fs-pre.target Note that this unit is generally not part of the initial transaction, unless the unit that wants to be ordered before all remote mounts pulls it in via a Wants= type dependency. So if I read it, nfs-common should pull in remote-fs-pre, but that leaves question what should pull in nfs-common itself. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] socket activated services and correct dependency mapping
On 24 Jul 2015 11:55, Dimitri John Ledkov dimitri.j.led...@intel.com wrote: On 24 July 2015 at 10:38, James Hogarth james.hoga...@gmail.com wrote: I want a user to be able to systemctl start sslh and use listening addresses in /etc/sslh.cfg as always (so I'm reluctant to put a straight Sockets= in the service unit file) but as it stands the lazy You can write a generator which will parse /etc/sshlh.cfg and drop e.g. $1/sslh.socket.d/sshlh-cfg.conf with contents [Socket] ListenStream=... That way e.g. you can enforce that config file is still fully honoured as canonical place to set ports. Checkout generators at http://www.freedesktop.org/wiki/Software/systemd/Generators/ Or e.g. look at /run/systemd for things that got generated by various stuff (e.g. like the fstab generator). Oh I love that idea! It didn't even occur to me but it's perfect for it... The configuration file is designed to be read with libconfig anyway which is already on the system making it pretty trivial. Thanks for that reminder - will arrange this later on this week :) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fstab generator and nfs-client.target
2015-07-25 3:18 GMT+02:00 Rich Freeman r-syst...@thefreemanclan.net: I noticed that mount units for nfs shares created by the generator do not Want=nfs-client.target or similar. That means that if you don't explicitly want nfs-client in your configuration then nfs shares will get mounted, but services like rpc-statd-notify.service won't run. Would it make sense to have the generator add the nfs-client target as a want to nfs mount services it creates? remote mount units do have a After remote-fs-pre.target ordering and tools like nfs-common/rpcbind are supposed to hook up into remote-fs-pre.target. http://www.freedesktop.org/software/systemd/man/systemd.special.html#remote-fs-pre.target -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
